[Epsilon] Modeling project build utilities to be deleted from Jenkins?

Summary

We are preparing a new minor release for Epsilon, and we noticed that one of the utilities we use to manage our composite update site from Jenkins was moved to a folder called /shared/modeling.deletemeafter013025. We'd like to know what to do from February 2025 onwards.

Steps to reproduce

We have a (now working after noticing the rename of /shared/modeling: please do not re-run) release-logistics Jenkins job that uses the manage-composite.xml tool from the Modeling Project to add the update site for a new stable release to the main composite update site.

What is the current bug behavior?

The job has succeeded after we used some ls calls to find out where /shared/modeling had gone and tweaked the job accordingly, but we are now concerned that these tools will not be available anymore after January 2025.

Could you clarify if these are being dropped altogether, or if they are being moved elsewhere? Should we just get a copy of manage-composite.xml and keep it somewhere ourselves?

What is the expected correct behavior?

We would normally expect the Modeling Project build tools to be available somewhere from Jenkins, and hopefully documented somewhere other than the now-archived wiki page.

Relevant logs and/or screenshots

See the log of this run of the job, where we had commented out everything except the use of this shared utility while trying to figure out what had happened to it:

https://ci.eclipse.org/epsilon/job/release-logistics/134/

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

We have found a workaround for the issue (we located where manage-composite.xml had been moved to), but we would like to know what we should do from February onwards.

added IT-prioritylow IT-severitylow service:jenkins statetodo team:releng labels

Hi, I am interested in contributing to resolving this issue. I have reviewed the problem description and the related logs. I’d like to propose a plan for addressing this.

Understanding : From what I understand, the issue is related to the relocation of the manage-composite.xml utility, which has impacted the Jenkins job for managing the composite update site. There is uncertainty about whether this utility will remain available after January 2025.

I suggest the following steps: Backup the manage-composite.xml script to ensure continued availability. Update the release-logistics Jenkins job to reference the new location. Test the updated job to ensure it works as expected. Reach out to the Eclipse Modeling Project team for clarification on the future availability of the utility. Document the process for the project's reference.

"Does this approach align with the project’s expectations? If there are additional considerations, please let me know so I can incorporate them."

Any updates on this? @emerks - what do you use for releases now?

Sorry, I have no clue about who created these utilities.

Most of the projects for which I manage release engineering are using this:

https://eclipse.dev/justj/?page=tools

E.g., EMF produces sites like this:

https://download.eclipse.org/modeling/emf/emf/builds/

Here are more examples:

https://eclipse.dev/justj/?page=tools#p2-manager-examples

Thank you for this! We'll look into this for Epsilon 2.8 onwards - apparently the utilities were still around today, so we've done Epsilon 2.7 with them :-).

Should we just get a copy of manage-composite.xml and keep it somewhere ourselves?

Yes, please copy all the tools you need to a different place (e.g. your downloads.eclipse.org directory) and let us know when you are done, so we can remove the folder /shared/modeling.deletemeafter013025.

@agarciad have the tools been copied to a different place?

Thanks for the reminder! Yes, we have copied the promotion tool that we used here:

https://download.eclipse.org/epsilon/build-tools/promotion/

I have checked its contents and I have not found any secrets or sensitive details there, but let me know if I have missed anything.