[releng] Rename nigtly to simply builds

[jonahgraham]

This is to better reflect that the builds are CI builds not strictly nightly.

In addition to accepting this PR the changes to make are:

• [ ] Configure the Jenkins job to change the Build Configuration -> Script path to be build.Jenkinsfile
• [ ] Rename the Jenkins job
• [ ] Delete the "nightly" directory on download.eclipse.org by editing* simple-script-job to do ${SSH} rm -rf ${DOWNLOAD_ROOT}/nightly

* If you want to create a new simple job to run a script, the steps are as follows. Note that soon, for simple download.eclipse.org operations there is the promise of a new web interface for managing artifacts there.

1. Navigate to CI home page
2. Click New Item in the top left
3. Name the item
4. Choose Freestyle Project
5. Press OK
6. Enable Build Environment -> SSH Agent (see Eclipse specific help)
7. Under Build choose Add build step and choose Execute shell
8. Type your script**
9. Save and run the build

** The Eclipse help has some info about how to ssh and scp. This is what I do:

Set environment variables as follows:

SSHUSER="genie.embed-cdt@projects-storage.eclipse.org"
SSH="ssh ${SSHUSER}"
SCP="scp"

DOWNLOAD_ROOT=/home/data/httpd/download.eclipse.org/embed-cdt

and then I can SSH or SCP like this:

${SSH} mkdir -p ${DOWNLOAD_ROOT}/temp
${SCP} file-to-upload ${SSHUSER}:${DOWNLOAD_ROOT}/temp/filename

[ilg-ul]

I'm not sure I understand the details, but nightly seemed not accurate and a bit confusing, so any change is an improvement.

[jonahgraham]

@ilg-ul I see you merged the PR 15 minutes ago - don't forget to do the other checklist items in the PR or come back to be if you have any questions.

[ilg-ul]

Ok, will come back to these issues, but it'll take me some time.

[ilg-ul]

@jonahgraham, if I try to access the https://ci.eclipse.org/embed-cdt/job/nightly/configure page, I get

Access Denied ilg@livius.net is missing the Job/ExtendedRead permission

Same for https://ci.eclipse.org/embed-cdt/job/nightly/confirm-rename, https://ci.eclipse.org/embed-cdt/view/all/newJob, and I guess for everything else.

What can we do to fix this?

[jonahgraham]

Weird - it works for me. File a bug against Community / CI-Jenkins on Bugzilla.

[ilg-ul]

Weird - it works for me.

It feels like the EF procedures were specially conceived to annoy and discourage developers :-(

File a bug against Community / CI-Jenkins on Bugzilla.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=565320

[ilg-ul]

And, since I don't see the openshift mentioned, I also did this:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=565321

I have no idea what this means. The documentation gives a lot of details, probably useful for those who already have a good experience with the CI environment, but quite opaque for newcomers. :-(

[ilg-ul]

Several new Jenkins scripts are now available.

The workflow is fully covered from development builds to the final release.

The two scripts that are part of the project were moved to scripts/jenkins.