Done. Let me know if you aren’t able to do something.
PTP is +3 BTW.
Greg
OK. Therefore, can you create two pipeline jobs, one called promote-a-build and one called promote-files-to-download. If I can edit them then I can run the builds and resolve the issues without further involvement.
Thanks Jonah Is that possible? I can give you permission to edit the current jobs, but I’m not sure if it’s possible to give you permission to create new ones.
Greg
Hi Greg,
Can you give me permission to edit/run jobs & create two new ones.
Thanks, Hi Jonah,
Thanks for offering to help with this. I don’t think there’s any way to give you access to the CI instance other than getting you committer status. I think I could give you permission to edit/run the current jobs or create new ones, if that would work for you. In any case I’d be happy to work with you to figure out how to fix the situation. Let me know what works best for you.
Regards, Greg
Hi Greg,
The release system you are using is very similar to what CDT does. I have already automated that with jobs on CDT's CI backed by Jenkinsfiles and scripts in github:
I can do the same for PTP as it is very much in CDT's interest to have one of our dependent and consumer projects continue to release regularly. I can probably do it for M1 this week if you have time, but it may be best to do your M1 contribution as normal and get this working for M2 in 6 weeks. What is your +N for PTP?
However as I am not a committer on PTP so I can't create new jenkins jobs and/or test them, so if you are interested I can work with you on this.
(As for the Foundations' contribution here, I don't think we can expect them to do individual project releng work - it would be nice if someone coordinated this kind of releng work across multiple projects, perhaps providing consistent Jenkinsfiles or similar for everyone to use. However I think at the moment that is a task no one want to takeover. This aspect of the conversation should be continued on cbi-dev.)
HTH, Jonah
That wouldn’t help PTP, however.
No, but it would help CDT :).
Jonah has done a masterful job of the CDT releng. Let's see what he can come up with for PTP.
Greg
As another option, we have discussed moving org.eclipse.remote down the stack a bit. We could take it over in CDT since we are using it for remote launching and we never got around to creating an IDE commons project, and probably won't at this point.
Thoughts? Doug. Hi Greg,
I too am curious, while you are discussing simrel, it seems you are really saying there won't be any future PTP relesases? Or is the problem just the simrel contribution?
Can you point me at what the PTP release scripting/process is so I can consider whether I, or others, can automate it?
Thanks Jonah
Hi,
The Eclipse Foundation are planning to remove ssh access to the build server, something we’ve been using for the last 15 years for our release process. Since the Foundation does not provide any standard mechanism for managing project releases, individual projects have had to develop their own processes. The PTP release process, which has been entirely adequate until now, requires some manual commands in order to verify the repository is valid and make it available. Without ssh access, we will need to develop a completely new release process that is driven from scripts that are run via Jenkins jobs. Currently there are no resources available to do this, and the Foundation has not offered any assistance or indication that they are intending to provide a standard release mechanism for projects to use. As a consequence PTP will need to withdraw from the SimRel and remove the Eclipse IDE for Scientific Computing from the downloads page. Unless I hear anything to the contrary, I plan to inform them of this at the end of the week.
Regards,
Greg
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________ ptp-dev mailing list ptp-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________ ptp-dev mailing list ptp-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________ ptp-dev mailing list ptp-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________ ptp-dev mailing list ptp-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/ptp-dev
|