Skip to content

New tokens needed for tools.cdt CI to allow dowloading artifacts

Summary

(I assume that?) with the change recently to restrict anonymous access to the CIs that CDT needs a token to be able to download, or some similar solution.

In CDT build & promotion scripts CDT's CI does things like:

wget https://ci.eclipse.org/cdt/job/cdt/job/main/678/artifact

to download artifacts from a specific build to promote them to download.eclipse.org.

Can CDT's CI get the needed token/etc to be able to download from within itself?

Steps to reproduce

See the failed wget near the end of https://ci.eclipse.org/cdt/view/all/job/promote-a-build/322/console

What is the current bug behavior?

Fail to download anonymously

What is the expected correct behavior?

Have token/someway to download from within Jenkins

Relevant logs and/or screenshots

See https://github.com/eclipse-cdt/cdt/blob/1ab88853ed443b0e05f822ec9a49404db1caa1c5/releng/scripts/promote-a-build.sh#L27 and https://github.com/eclipse-cdt/cdt/blob/1ab88853ed443b0e05f822ec9a49404db1caa1c5/releng/scripts/promote-a-build.sh#L41 where the wgets are done.

That script is called by this Jenkinsfile https://github.com/eclipse-cdt/cdt/blob/1ab88853ed443b0e05f822ec9a49404db1caa1c5/releng/promote-a-build.Jenkinsfile#L40

Priority

  • Urgent
  • High
  • Medium
  • Low

Severity

  • Blocker
  • Major
  • Normal
  • Low

Impact

I can't release CDT without resolving this. Ideally I will do a release on Monday the 25th, but can slip a little if needed.