Re: CVS Plugin Adpotion

[moritz...@gmail.com]

Hi all,
after releasing several bugfix- and security updates for the cvs-plugin I'm 
now no longer able to access a production CVS server anymore.
I would still be able to perform releases (e.g. security fixes), but cannot 
test changes in a "real" environment, so these would be "blind" releases.

The cvs-plugin is still marked as "open for adoption", which is totally 
true now. 

Thanks for all your help during the past releases!
Moritz


Mark Waite schrieb am Mittwoch, 25. März 2020 um 14:38:18 UTC+1:

> That's great.  Congratulations on the release.
>
>
> https://jenkins.io/doc/developer/publishing/documentation/#using-github-as-a-source-of-documentation
>   
> describes how to convert a plugin to host its documentation on GitHub.  
> Once a plugin is released that includes those changes, the documentation 
> will be copied from GitHub to plugins.jenkins.io.
>
> Or, you could merge my pull request - 
> https://github.com/jenkinsci/cvs-plugin/pull/51
>
> Mark Waite 
>
> On Wed, Mar 25, 2020 at 6:45 AM Moritz Rösel  wrote:
>
>> Hi all,
>>
>> thanks for your help and all the good documentation on releasing a plugin.
>> Right now I released cvs-2.15, that fixed the blocking "Excluded-Region 
>> Nullpointer" Bug.
>> cvs-plugin should now be functional again with latest jenkins releases.
>>
>> How can this page be updated?
>> https://plugins.jenkins.io/cvs/
>>
>> I will try to look into the other open issues in the next weeks.
>>
>> Best wishes
>> Moritz
>>
>>
>> Am Donnerstag, 12. März 2020 20:30:40 UTC+1 schrieb Moritz Rösel:
>>>
>>> Hi all,
>>>
>>> I already posted this request in April 2019 but unfortunately didn't 
>>> receive any response.
>>>
>>> https://groups.google.com/forum/#!searchin/jenkinsci-dev/cvs$20plugin%7Csort:date/jenkinsci-dev/3OvlIZFdA9M/7Z2eatXHCQAJ
>>>
>>> Since still some people are using the CVS plugin (>40k installs in Feb 
>>> 20) I want to push this topic again and offer to adopt the CVS plugin for a 
>>> maintenance release. I don't have time to maintain the plugin on the 
>>> long-term, but want to help current users getting a functional plugin 
>>> out-of-the-box in a recent jenkins installation.
>>>
>>> The pull requests are on GitHub for the worst issues, that make the 
>>> plugin stop working with latests jenkins releases.
>>> https://github.com/jenkinsci/cvs-plugin/pull/49
>>> This fix is optional, but would also help:
>>> https://github.com/jenkinsci/cvs-plugin/pull/50
>>>
>>>
>>> My github: https://github.com/mrmoritz01
>>> Same username mrmoritz01 on jenkins.io
>>>
>>> Best wishes
>>> Moritz
>>>
>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/e6bcf563-a2fb-4d75-93bd-e31753fc2024%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e3bc51d4-92ab-4416-a3c1-9105d100f828n%40googlegroups.com.

Re: GSoC 2021 - Please welcome Jenkins students!

[Alyssa Tong]

Welcome all to the Jenkins family ☺

On Thu, May 20, 2021 at 2:55 PM Oleg Nenashev 
wrote:

> Recording of the Jenkins community bonding kick-off on May 19, 2021:
> https://youtu.be/5nR2eNa8HbQ. We discussed the project selection results,
> thanked all participants, discussed next steps and the community bonding
> expectations. If you are a student or a mentor not sure about the community
> bonding steps and expectations, please watch it!
>
> On Tue, May 18, 2021 at 1:06 AM Oleg Nenashev 
> wrote:
>
>> Dear all,
>>
>> The GSoC 2021 projects have been announced by Google today. The
>> Continuous Delivery Foundation will have 6 projects this year, and five of
>> them will be focused on Jenkins. You can find all the projects here
>> .
>> Please welcome the GSoC 2021 students!
>>
>>- Shruti Chaturvedi, "CloudEvents Plugin for Jenkins: Consume and
>>Emit CloudEvents". Mentors: Vibhav Bobade, Jeff Pearce, Mauricio Salatino
>>- Harshit Chopra, "Git credentials binding for sh, bat, and
>>powershell", Mentors:  Mark Waite, Justin Harringa, Rishabh Budhouliya
>>- Akihrio Kiuchi, "Jenkins Remoting Monitoring", Mentors: Oleg
>>Nenashev, Sumit Sarin, Darshan Kansagara
>>- Pulkit Sharma, "Security Validator for Jenkins Kubernetes
>>Operator", Mentors: Bartek Antoniak, Sylwia Brant, Jakub Al-Khalili
>>- Aditya Srivastava, "Semantic Versioning Plugin for Jenkins",
>>Mentors: Gareth Evans, Kristin Whetstone, Olivier Vernin, Allan 
>> Burdajewicz
>>- (+) In addition to 5 Jenkins projects, Daniel Ko will be working on
>>try.spinnaker.io, Mentors: Dan Johnston, Fernando Freire, Cameron
>>Motevasselani
>>
>> During the next 3 weeks the GSoC teams will work on the community
>> bonding, including but not limited to: getting introduced to each other and
>> the key stakeholders, setting up the communication channels, forming the
>> project plan, and doing knowledge transfers. We invite all community
>> members to reach out to the project teams if you are interested in a
>> project and want to contribute there and/or to be informed about the
>> progress. Any assistance to the students will be always appreciated.
>>
>> All the listed projects have high value to the Jenkins community,
>> particularly for public cloud deployments and for the ongoing Jenkins
>> software delivery pipelines rework. We are looking forward to working with
>> the students and mentors this summer, welcome everyone!
>>
>> Best regards,
>> Oleg Nenashev
>> CDF GSoC Org Team
>>
>> P.S: See the GSoC sub-project mailing list to know more about the GSoC
>> projects announcement:
>> https://groups.google.com/g/jenkinsci-gsoc-all-public/c/EkwY7o2Jgzo . We
>> will also have the regular office hours on Wednesday, 2PM UTC. See
>> https://www.jenkins.io/events for the links
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBB%2BG9EZqCsjnMeMkYx8OQ-bd0y4XkW8Kua47gZu%2BBPYw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAMBsfbts-85AOV7DxqH4v9xgzBJqBQSuM48Kz%3DjohJ1gMUfuAA%40mail.gmail.com.

Re: Problems with env variable

[yusuf zainee]

Basically,
Im not able to alter the value in the path env variable. One way is to have
a new field where in the user can pass the desired path value and then i
pick that value and use it in my java files. But im sure there is a more
elegant solution for this.

On Mon, 24 May, 2021, 20:42 yusuf zainee,  wrote:

> Hi,
> I'm facing a problem wrt the PATH env variable.
> 1. In pipeline, i have a script,
> pipeline {
>
> agent {
> label 'master'
> }
> environment {
> PATH="/usr/local/bin:$PATH"
>}
>stages {
> stage ('build') {
> steps {
> echo "PATH=$PATH"
> echo pwd()
> echo "running crda analysis"
> crdaAnalysis file:'', crdaKeyId:'',
> cliVersion:''
> echo "finished"
> }
> }
> }
> }
> In the logs i can see
>
> *PATH=/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin*
> but when i try to access the value in the step class and print 
> *System.getenv("PATH")*, i see
>
> *PATH:/sbin:/usr/sbin:/bin:/usr/bin*
>
>
> 2. In the build step, I am facing the same problem.
>
> I tried setting the Path in the global env variable. Didnt work.
> I tried to provide the value in the (execute shell), but when i try to view 
> the value of PATH in the plugin java class, i again see the same 
> *PATH:/sbin:/usr/sbin:/bin:/usr/bin*
>
>
> Can someone please tell me whats going wrong here
>
>
> Regards,
>
> Yusuf
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAHf8TqjgC3AjTg1G0syyCk%3DWp9YQ4FSKjp-PNa_kkd3Ui_X4ZQ%40mail.gmail.com.

Re: [workflow-durable-task-step-plugin] Add tool installer for Powershell Core

[Jesse Glick]

On Fri, May 21, 2021 at 5:51 PM Tim Van Holder 
wrote:

> PowerShell Core is multi-platform and installable via zip or tarball.
> As such, I'd be inclined to want to add a tool installer for it
>

The `ToolInstallation` system is generally deprecated. Modern CI setups are
expected to use VMs or containers with appropriate tools preinstalled. So I
would probably recommend creating a separate plugin for the likely small
number of users who would benefit. Or better yet, just check whether
the existing
plugin

works
for you.


> a withPwsh (or withPowerShellCore?) step would also make sense, to put a
> particular install in PATH for a delimited set of steps (as I understand
> it, with the tool section, it always applies to an entire stage)
>

There is limited flexibility in Declarative syntax. For Scripted syntax,
this just sounds like it would be better covered by the general
JENKINS-28718 . A dedicated
block-scoped step makes sense for logic that does something more
complicated than bind a `ToolInstallation` to a `$PATH` entry.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2Q66ArFPTDY2V8eeQn3t4AR_8giQc%3DtsptoDX5n5e8aQ%40mail.gmail.com.

Problems with env variable

[yusuf zainee]

Hi,
I'm facing a problem wrt the PATH env variable.
1. In pipeline, i have a script,
pipeline {

agent {
label 'master'
}
environment {
PATH="/usr/local/bin:$PATH"
   }
   stages {
stage ('build') {
steps {
echo "PATH=$PATH"
echo pwd()
echo "running crda analysis"
crdaAnalysis file:'', crdaKeyId:'',
cliVersion:''
echo "finished"
}
}
}
}
In the logs i can see

*PATH=/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin*
but when i try to access the value in the step class and print
*System.getenv("PATH")*, i see

*PATH:/sbin:/usr/sbin:/bin:/usr/bin*


2. In the build step, I am facing the same problem.

I tried setting the Path in the global env variable. Didnt work.
I tried to provide the value in the (execute shell), but when i try to
view the value of PATH in the plugin java class, i again see the same
*PATH:/sbin:/usr/sbin:/bin:/usr/bin*


Can someone please tell me whats going wrong here


Regards,

Yusuf

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAHf8Tqj%2B0j_%3DAveqsBzybGw78yeEGhCnMp2r_b1zA9DBeu0-NQ%40mail.gmail.com.