Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-docs-dev] Mylyn Docs and p2 repository locations
Steffen,

See comments inline below:

On Fri, Mar 10, 2017 at 8:04 AM Steffen Pingel <steffen.pingel@xxxxxxxxxxx> wrote:
Hi David,

that sounds like a good plan. One thing I'm wondering is where maintenance releases are going to be published, e.g. 3.0.1? Would that override the 3.0 release or would there be a separate p2 repository? It's important that we have a stable p2 repository location for every release to enable consumer to point their builds at a specific release.

Agreed.  My thinking is that we would publish 3.0.2, 3.0.3, etc. all to the same p2 repository - in other words, when a point release becomes available the prior point release would be removed, but the location would stay the same.  So anyone pointing to the location would get the latest point release.
 

Mylyn also produces "integration" builds which is why the drops location exists. This makes is easy to provide multiple builds for a particular release stream. I assume WikiText will only be published to the nightly site and there is no need for integration builds or staging release builds?

I haven't heard of a need so far to provide multiple builds for a release stream.  It could be that I simply don't understand why they would be needed.  My plan right now is to not provide "integration" builds.  Should we adjust that plan?
 

Have you thought about how consumers would install WikiText builds into Eclipse? Mylyn provides composite repositories for each Eclipse release stream, e.g. http://download.eclipse.org/mylyn/releases/neon/ which makes it very simple for users to get the right version for their Eclipse installation. 

My suggestion would be to include the appropriate WikiText version in that composite site and assume that Mylyn Docs users will continue to use that as the source for installing WikiText into Eclipse. We can add a step to the WikiText release build to automate updating of those composite sites.

To be sure that I'm understanding correctly, are you suggesting that we continue to distribute Mylyn Docs for the EPP release train and other Eclipse installations via the Mylyn composite site?  
If so, that sounds good to me.  I don't see a need to change it or for users to have yet another update site to worry about.

Some help on updating the composite sites would be really great.  Is there anyone interested in taking that on?

David
 

Steffen



On Fri, Mar 10, 2017 at 1:46 AM, David Green <david.green@xxxxxxxxxxx> wrote:
I've setup a build here: https://hudson.eclipse.org/mylyn/view/Mylyn%20Docs/job/mylyn-docs-release/

The initial build failed because wiki.eclipse.org is offline and we have an integration test that hits the wiki.  We can try this one again once the wiki is back up.

David

On Thu, Mar 9, 2017 at 4:08 PM David Green <david.green@xxxxxxxxxxx> wrote:
Devs,

I've got the nightly build producing signed p2 artifacts for all of Mylyn Docs.  This was the last tough step in separating the Mylyn Docs release from Mylyn - we're now in a position where we can release signed artifacts.

So far the p2 repository for Mylyn Docs is here: http://download.eclipse.org/mylyn/snapshots/nightly/docs/
What we need is a location for Mylyn Docs release artifacts.  

Mylyn releases their artifacts under http://download.eclipse.org/mylyn/releases/<version>, e.g. http://download.eclipse.org/mylyn/releases/3.21 which is really just an alias to something under http://download.eclipse.org/mylyn/drops/<version>  e.g. http://download.eclipse.org/mylyn/drops/3.21.1/v20161129-2023/

I'm proposing to use the following for Mylyn Docs releases:
http://download.eclipse.org/mylyn/docs/releases/<version>, e.g. http://download.eclipse.org/mylyn/docs/releases/3.0 
The thinking is that we can have a release build that builds off a tag (e.g. wikitext.core-3.0.2) and publishes to the appropriate location automatically.  By building off the tag produced by the wikitext.core release build we'll end up producing p2 artifacts from the same commit that was used to produce the artifacts that we get on Maven Central.

So the release process would end up being something like:
1. build wikitext.core using the maven-release-plugin and publish in the Nexus staging area for Maven Central
2. build the Mylyn Docs release from the tag created in step 1, and automatically publish to download.eclipse.org
3. release the staged artifacts to Maven Central

Let me know if you have any feedback.

David

--


David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx

--


David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx


_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev



--
Steffen Pingel
Staff Software Engineer
http://tasktop.com
_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev
--


David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx

Back to the top