So we were approved (and kinda excitedly at that).
I've sent invites to the board and the officers. I'm going to make vaults
for each officer position, and the board, and then after that I can let
kinda self management happen?
Gavin
On Fri, Dec 10, 2021 at 5:15 PM Gavin Mogan wrote:
> I've
Backporting has started and the RC is scheduled for 2021-12-20
Candidates: https://issues.jenkins-ci.org/issues/?filter=12146
Fixed:
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.319.2-fixed
Rejected:
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.319.2-rejected
I've moved stapler to Jenkinsci as part of
https://issues.jenkins.io/browse/INFRA-2908
Core team has access
Jesse has taken care of most of the rest of the proposals already
On Wed, 26 May 2021 at 17:03, Oleg Nenashev wrote:
> Thanks to Kohsuke for your approval! And thanks to Kohsuke and
Thank you Kris and Oleg for your responses. Your inputs are noted and I
will circle back once we have more on project ideas and mentors.
BR,
alyssa
On Thu, Dec 16, 2021 at 3:42 AM Kris Stern wrote:
> Hi Alyssa and Oleg,
>
> I am interested in volunteering and mentoring in GSoC 2022 for
On Thu, Dec 16, 2021 at 10:44 AM 'jn...@cloudbees.com' via Jenkins
Developers wrote:
> you are still tagging the commit "[maven-release-plugin] prepare release
> project-a.bcd" the only difference is that these commits never appear on
> the mainline branch (master)
>
Yes, this is possible.
>> Using MRP as I described would not confuse any tool
>Depends on the tool. The problem would be that a source checkout at the
commit/tag would, if loaded as a project rather than a deployed artifact,
have a version different from the artifact. (Also true in JEP-229
components by default,
On Wed, Dec 15, 2021 at 4:35 PM James Nord wrote:
> The plugin pom probably needs to remove a lot of cruft that makes it work
> with older release now.
>
I tried in https://github.com/jenkinsci/plugin-pom/pull/457 but apparently
got it wrong; if someone has time to dig deeper that would be
Hi Alyssa and Oleg,
I am interested in volunteering and mentoring in GSoC 2022 for Jenkins. In
particular, I would like to work on the project idea "Jenkinsfile Runner Action
for GitHub Actions" as listed in Oleg's email.
Maybe I should introduce myself a bit to begin. I started contributing
On Thu, Dec 16, 2021 at 10:38 AM 'simon' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> how can I access the current request path* from inside a class extending
> `hudson.model.Action`? I would like to extend the sidebar link plugin to
> add a reference to the url.
>
Hi all,
Quick update here from the yesterday's governance meeting:
- The LFX EasyCLA support ticket is still open for jenkinsci and
jenkins-infra organizations. Stapler maintainers can already adopt it if
they are ready & want to try
- I pinged the LFX support team to get the
Hi Alyssa,
Thanks a lot for taking care of it! I might be able to participate as org
admin in some capacity, but I cannot commit much time next year. My
personal situation is still complicated, and I'm not sure how much time I
will be able to dedicate to Jenkins in general. I will be also
Hello,
how can I access the current request path* from inside a class extending
`hudson.model.Action`? I would like to extend the sidebar link plugin to add a
reference to the url.
Regards,
Simon
* e.g. job// or view//job//
--
You received this message because you are subscribed to the
12 matches
Mail list logo
