Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 559766 - Nightly package builds
Summary: Nightly package builds
Status: RESOLVED FIXED
Alias: None
Product: EPP
Classification: Technology
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: later   Edit
Assignee: Jonah Graham CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-02 07:37 EST by Wim Jongman CLA
Modified: 2020-02-06 10:20 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wim Jongman CLA 2020-02-02 07:37:19 EST
I am working with a couple of end-user that have tested a solution to platform using the nightly SDK build. The fix solved their problem.

Now they are asking for the (j2ee) package containing this fix so I went looking if the EPP provides nightlies and I found the nighty link on the epp homepage [1]

Unfortunately, the link is dead. 

Can you take look at this? 

[1] https://www.eclipse.org/epp/
Comment 1 Jonah Graham CLA 2020-02-02 19:25:56 EST
Hi Wim. My solution for now will unfortunately be to simply remove the text. Even if we do a nightly EPP build, it will have the same content from platform SDK as the platform updates the simrel only on milestones and RCs.

(With Markus' recent resignation of project lead of EPP there is no lead now, so there are lots of discussions on how to do this going forward. One of the proposals would be to have continual integration for simrel and EPP, but no one has signed up to do that work yet.)
Comment 2 Jonah Graham CLA 2020-02-02 20:40:06 EST
I suspect the equivalent of what the link used to point to could now be https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/ this is rebuilt for each simrel contribution, so generally quite often in days leading up to a Milestone or Release Candidate build, but not so much the rest of the time.
Comment 3 Wim Jongman CLA 2020-02-04 04:19:18 EST
(In reply to Jonah Graham from comment #2)
> I suspect the equivalent of what the link used to point to could now be
> https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/ this is rebuilt
> for each simrel contribution, so generally quite often in days leading up to
> a Milestone or Release Candidate build, but not so much the rest of the time.

Yes. I think we are fine if we can just let the people upgrade to the latest SDK from within the various packages. 

This is a manual process now. Maybe we can introduce an "activate nightly repositories" switch somewhere that would allow "check for updates" to update from the SDK/EPP nightlies.  

It would be nice if the EPP website is taken care of though. Are you an EPP committer?
Comment 4 Jonah Graham CLA 2020-02-04 07:38:39 EST
I am an EPP committer. I am carrying the torch for 2020-03 M2[1], but we are looking at doing shift for EPP going forward. 

[1] https://www.eclipse.org/lists/epp-dev/msg05677.html
Comment 5 Wim Jongman CLA 2020-02-04 07:49:36 EST
(In reply to Jonah Graham from comment #4)
> I am an EPP committer. I am carrying the torch for 2020-03 M2[1], but we are
> looking at doing shift for EPP going forward. 
> 
> [1] https://www.eclipse.org/lists/epp-dev/msg05677.html

Great. If I can assist you then let me know.

I can make the website patch. What is your decision about the nightly link, chief?
Comment 6 Jonah Graham CLA 2020-02-04 08:17:09 EST
I was going to relabel it to be something along the lines of it being continuous builds based on when simrel or EPP content changes. (may need some wordsmithing)
Comment 7 Eclipse Genie CLA 2020-02-06 10:03:19 EST
New Gerrit change created: https://git.eclipse.org/r/157281
Comment 9 Eclipse Genie CLA 2020-02-06 10:12:08 EST
New Gerrit change created: https://git.eclipse.org/r/157285
Comment 11 Eclipse Genie CLA 2020-02-06 10:15:22 EST
New Gerrit change created: https://git.eclipse.org/r/157286
Comment 13 Jonah Graham CLA 2020-02-06 10:20:07 EST
I fixed the webpage - but only in this limited way. There are lots of other out of date items that need addressing.