Re: [ptp-dev] Withdrawal from SimRel

[Greg Watson <g.watson@xxxxxxxxxxxx>]

This change would affect both the SimRel and future releases of PTP. 

SimRel requires a stable repository for each milestone build, which are currently promoted to the aggregate http://download.eclipse.org/tools/ptp/builds/photon/milestones/. The process requires copying the nightly build from http://download.eclipse.org/tools/ptp/builds/nightly/ into the aggregate and updating the composite* files. In addition, when PTP releases a new version, we create a version numbered release directory in https://download.eclipse.org/tools/ptp/updates/. There are another set of release directories that follow this pattern for the Remote project. 

Currently, a build only creates the nightly (and remote/nightly) directory. This would still be available, as well as the artifacts from the Jenkins build job. However, nightly is written over each time the job runs, so the only stable location would be the build artifacts in the job.

Since activity is fairly low currently, I recently simplified the build process to dispense with nightly/release/bug fix builds and just use nightly.

The main Jenkins jobs are the ‘pip-build’ and ‘remote-build’ jobs in the https://ci.eclipse.org/ptp instance.

Regards,

Greg

On Jul 15, 2019, at 10:08 AM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:

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 

On Mon., Jul. 15, 2019, 09:24 Greg Watson, <g.watson@xxxxxxxxxxxx> wrote:

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