Environment secrets not working in Origin repo based Project

Support Bug Reports
, ,
5

Hey @sam74s, thanks for the detailed report and the IDs, they made this quick to trace.

What’s going on: your Project started on the temporary repository that a new project gets before it’s named. After you named it sam74s/aiao-v3, the Project’s agents kept starting on that earlier temporary name. Because of that, they don’t match the environment you set up for sam74s/aiao-v3, and secret injection is skipped for them. That’s why every worker reports no environment, why all four variables are unset, and why the active build id is refused. I’ve flagged this to the team.

In the meantime, could you try this and tell me what you see?

  1. Open a new Cloud Agent (not inside the existing Project) and pick sam74s/aiao-v3 as the repository.
  2. Pick the sam74s/aiao-v3 environment if you’re asked for one.
  3. Once it starts, ask it to run test -n "$NAME" && echo set || echo unset for each of the four names. Values won’t be printed.
  4. Reply with whether each one says set or unset, and the agent’s ID.

If that works, a new Project created from sam74s/aiao-v3 should get the secrets too.

On the environment panel: secrets are saved on their own from the Secrets section (New Secret), and the Save button only covers changes to the install and start scripts. If a secret you added there no longer appears in the Secrets list after you reload the page, please tell me which page you added it from.