In our latest builds (this is the one from our master branch three hours ago) the first two jobs, which are conditional on two secret environment variables, were apparently not run. However, the two variables are made available to the other jobs (we don’t use them there, but at least the logs say so). This build from two days ago is the last complete build of the master branch.
By the way, for some reason global environment variables are now shown on the overview page, which clutters it and wasn’t the case so far (see the two results linked above).
@BanzaiMan I’m facing a similar problem. My project’s build keeps failing when I use encrypted env variables and But they work fine when they are not encrypted.
I don’t see any build that has an if condition to add jobs conditionally, so whatever issue you are having with your configuration does not seem related to this issue.
However, I wasn’t able to restart an existing build to check it (via “Restart build” button) as the new build didn’t include previously ignored jobs (see this restarted and canceled build of the master branch).
Global env variables are still listed. Was that change on purpose?
In the build overview where all jobs are listed. The global variables (defined in env.global) are now listed for each job (looks like this, includes duplicates as some of the defaults are overridden for individual jobs). This is how it looked before last week (i.e. only the variables defined in jobs.include.[].env were listed), which was a bit clearer.