Conversation

Notices

1. Embed this notice
   Jan Wildeboer 😷:krulorange: (jwildeboer@social.wildeboer.net)'s status on Friday, 13-Dec-2024 04:32:41 JST Jan Wildeboer 😷:krulorange:

   • Codeberg.org

   Le sigh. Feels that every time I publish a blog post, @Codeberg tells me I need to change something somewhere in my config because something somewhere has changed with Woodpecker or something else. Right now it is something somehow has changed with passing secrets, so I apologise if my blog looks weird while I try to sort things out.

   • Embed this notice
     Marco 🦝 :verified: :grumpycat: (m2vh@mastodontech.de)'s status on Friday, 13-Dec-2024 05:15:40 JST Marco 🦝 :verified: :grumpycat:

     • Codeberg.org

     @jwildeboer @Codeberg maybe escape them when you use them? If they are preprocessed then :
     echo $${CBTOKEN}

     Should be resolved to :
     echo tokenvalue

     Your missing the {{}}?

   • Embed this notice
     Codeberg.org (codeberg@social.anoxinon.de)'s status on Friday, 13-Dec-2024 05:28:35 JST Codeberg.org

     @jwildeboer Honestly, I was also pretty annoyed by this. Take a look at https://codeberg.org/Codeberg-Infrastructure/ci-status-pings/commit/f314d99892b309f92a21c19f05394abeb9734d11 and try to change your pipelines in a similar way. ~f

   • Embed this notice
     Marco 🦝 :verified: :grumpycat: (m2vh@mastodontech.de)'s status on Friday, 13-Dec-2024 06:50:29 JST Marco 🦝 :verified: :grumpycat:

     • Codeberg.org

     @jwildeboer @Codeberg found the warning. It looks like you need to paas the secrets into a setting or environment variable before using it in a command. Actually you use a declared secret. Maybe put
     environment:
     CBTOKEN_ENV:
     from-secret: cbtoken

     between your line 8 and 9
     and reference in command like ${{CBTOKEN_ENV}}.

     BTW:
     The documentation is age-insensitive 😁.
     It's just not clear. 😉

   • Embed this notice
     Marco 🦝 :verified: :grumpycat: (m2vh@mastodontech.de)'s status on Friday, 13-Dec-2024 07:35:21 JST Marco 🦝 :verified: :grumpycat:

     • Codeberg.org

     @jwildeboer @Codeberg my guess, because its yaml:

     secrets: [token1, token2]

     environment:
     TOKEN_1:
     from-secret: token1
     TOKEN_2:
     from-secret: token2

     commands:
     - echo ${{TOKEN_1}}
     - echo ${{TOKEN_2}}

     That's how i understand the docs

   • Embed this notice
     Marco 🦝 :verified: :grumpycat: (m2vh@mastodontech.de)'s status on Saturday, 14-Dec-2024 06:41:28 JST Marco 🦝 :verified: :grumpycat:

     in reply to

     • Codeberg.org

     @jwildeboer @Codeberg the update would be the use of env vars in commands instead of referencing the secrets directly. That could explain the warning message that secrets are not allowed.

   • Embed this notice
     Codeberg.org (codeberg@social.anoxinon.de)'s status on Saturday, 14-Dec-2024 07:20:43 JST Codeberg.org

     • Marco 🦝 :verified: :grumpycat:

     @jwildeboer
     Have you tried `from_secret` instead of `from-secret`? Might do the trick (not tried, though).

     BTW, Codeberg also offers hosted Forgejo Actions as of recently, and feedback is very welcome: https://codeberg.org/actions/meta/
     @m2vh

   • Embed this notice
     Marco 🦝 :verified: :grumpycat: (m2vh@mastodontech.de)'s status on Saturday, 14-Dec-2024 07:24:50 JST Marco 🦝 :verified: :grumpycat:

     • Codeberg.org

     @jwildeboer @Codeberg hmmm... May i suggest this version, but with the secrets declared? https://codeberg.org/jwildeboer/jwildeboersource/src/commit/bac77e219b9cce4925bdd7311e7b56f32e61b8ac/.woodpecker.yml

     $${VAR_NAME} looks like the docs. But I'm missing the

     secrets: [ secret1, secret2]

     But i might be wrong, because i followed your files on my mobile phone, and missed something.

     🤔🙏🤞

   • Embed this notice
     Codeberg.org (codeberg@social.anoxinon.de)'s status on Saturday, 14-Dec-2024 07:26:31 JST Codeberg.org

     • Marco 🦝 :verified: :grumpycat:

     @jwildeboer
     TOKEN_ENV vs CBTOKEN_ENV mismatch? Your history looks frustrating, though. I don't know when Woodpecker 3.0 will be deployed, but it should continue working until then.
     @m2vh

   • Embed this notice
     preferred (preferred@expressional.social)'s status on Saturday, 14-Dec-2024 07:40:03 JST preferred

     • Codeberg.org

     @jwildeboer @Codeberg

     You could almost make a blog-post. In case this is something most people will run into, I mean.

   • Embed this notice
     preferred (preferred@expressional.social)'s status on Saturday, 14-Dec-2024 18:10:16 JST preferred

     • Codeberg.org

     @jwildeboer @Codeberg 💝 ☑️ 🥇

   • Embed this notice
     Marco 🦝 :verified: :grumpycat: (m2vh@mastodontech.de)'s status on Saturday, 14-Dec-2024 19:54:25 JST Marco 🦝 :verified: :grumpycat:

     • Codeberg.org

     @jwildeboer @Codeberg

     yeah. 🥳

     Just by the power of fediverse.

     -🫷😉👇_