Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338726 - manage MPC participation in Indigo
Summary: manage MPC participation in Indigo
Status: CLOSED FIXED
Alias: None
Product: MPC
Classification: Technology
Component: Install (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: 1.1   Edit
Assignee: Benjamin Muskalla CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 339155 354949
Blocks:
  Show dependency tree
 
Reported: 2011-03-02 15:14 EST by Steffen Pingel CLA
Modified: 2012-11-23 13:46 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2011-03-02 15:14:06 EST 
The MPC contribution for Indigo needs to be updated following the Indigo milestone schedule.

http://wiki.eclipse.org/Indigo
Comment 1 Steffen Pingel CLA 2011-03-02 15:15:00 EST 
Benjamin, can you update the contribution to the latest nightly? It would be good to make the fix for bug 334686 available.
Comment 2 Benjamin Muskalla CLA 2011-03-07 08:42:14 EST 
Steffen, I could update the indigo contributions to use the artifacts from hudson but I think we should rather upload the changes to the download server. Currently, I don't have permissions to change anything in downloads/mpc on download.eclipse.org
Also, the composite repos over there point to the old mpc jobs (eg. see nightly/compositeContent.xml).

How should we proceed on this one?
Comment 3 Steffen Pingel CLA 2011-03-07 13:58:09 EST 
I have automated the upload portion for Mylyn. We could do the same changes for MPC and let the hudson job propagate the bits to the download server.
Comment 4 David Green CLA 2011-03-07 16:08:41 EST 
That sounds like a good idea Steffen.
Comment 5 Benjamin Muskalla CLA 2011-03-08 07:30:09 EST 
Yes, that would be great! Once the builds are propagated, I can update the b3 contribution file
Comment 6 Steffen Pingel CLA 2011-03-08 16:01:47 EST 
It's all done. I updated the contribution file so the next green Indigo build should pick up the latest.
Comment 7 David Green CLA 2011-03-10 12:54:16 EST 
Thanks Steffen.  Do we need to do anything special to trigger these builds, or do they poll Git?
Comment 8 Benjamin Muskalla CLA 2011-03-10 14:08:31 EST 
Currently the regular builds are triggered daily, the release build needs to be triggered manually.
Comment 9 David Green CLA 2011-03-10 14:27:39 EST 
Is there a reason why one of our builds isn't polling Git?  It would be great to get a CI build.  BTW, I used to be able to trigger a build manually if I was logged in to Hudson, it seems that I no longer have permission.
Comment 10 Benjamin Muskalla CLA 2011-03-10 14:40:38 EST 
Will add you to the builds
Comment 11 Benjamin Muskalla CLA 2011-03-10 14:46:46 EST 
David, added you as releng user to all builds. Configured git polling (30m) on all builds except release.
Comment 12 Steffen Pingel CLA 2011-03-10 15:17:07 EST 
release builds are promoted to Indigo. That's why they are intentionally manual. Considering the rate of change on MPC I don't see any need to automate nightly builds.

David, why did you assign this bug to the inbox?
Comment 13 David Green CLA 2011-03-10 15:26:51 EST 
Great, thanks.

(In reply to comment #12)
> David, why did you assign this bug to the inbox?

that was accidental: assigning back to you Steffen.
Comment 14 Benjamin Muskalla CLA 2011-04-27 15:15:23 EDT 
Taking this for M7.
Comment 15 Benjamin Muskalla CLA 2011-04-27 15:24:23 EDT 
Promoted 1.1.0/I20110427-1505 as M7 contribution for Indigo.
Comment 16 Benjamin Muskalla CLA 2011-09-08 08:50:07 EDT 
Promoted 1.1.1.I20110907-0947 as SR1 RC3
Comment 17 Ian Skerrett CLA 2012-11-23 13:46:46 EST 
Indigo is long done