Re: [Event] DevOps World | Sept 22-24: Jenkins volunteers needed

[Marky Jackson]

Count me in!

> On Aug 24, 2020, at 3:45 PM, Alyssa Tong  wrote:
> 
> 
> Hi All,
> 
> The Jenkins project, along with CDF will be at DevOps World's virtual event 
> this coming Sept 22-24, 2020. We are looking for Jenkins volunteers to help 
> staff the virtual booth, it is a 1 hour commitment in the comfort of your 
> home/office - of course we would not decline if you'd like to give more than 
> 1 hr ☺. Duties include answering Jenkins technical questions by attendee(s). 
> The signup sheet is  HERE.
> 
> If you have questions pls reach out.
> 
> Thank you,
> alyssa
> -- 
> 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/CAC9wNawdccTAKa4PrrhO62BJn9e5%2BToBVHvSors%3DbFR5kCePyQ%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9202AF94-C236-4CA3-8353-58B84397C302%40gmail.com.

Re: HTML Publisher pipeline syntax

[Richard Bywater]

Looks like the issue is with your reportDir. In your case I think you'd
want this set to simply "coverage-results" assuming there is a index.html
in that directory. If the index.html only exists in the subdirectories of
coverage-results (which I think might be the case?) then reportFiles should
be something like "*/index.html" or "**/index.html" (exact syntax alludes
my brain right this second).

Note that if you are wanting to keep the reportFiles and reportTitles in
sync, you'll probably want to explicitly add each directory as a reportFile
(e.g.
"coverageDir1/index.html,coverageDir2/index.html,coverageDir3/index.html)

Hope that helps - I have only had a casual look in between my day job jobs
but hopefully it gets you in the right direction.

Richard.

On Tue, 25 Aug 2020 at 09:43, Steven Heuertz 
wrote:

> Hi,
>
> I'm working with a pipeline that builds a bunch of npm packages in a
> monorepo. Our commands are run on each package individually, so we have
> individual test/lint results in each package. I'm trying to pull all of the
> results into a single html report. To make this easier, I'm copying the
> reports into a central folder, and trying to build the report from there:
> pipelineContext.echo "Publishing jest results"
> pipelineContext.sh(script: 'mkdir coverage-results')
> List reportTitles = []
> changeSet.each {
> String coverageDir = it.packageJson.name.replace('/', '_')
> pipelineContext.sh(script: "mkdir -p coverage-results/${coverageDir}")
> pipelineContext.sh(script: "cp -R ${it.path}/coverage/lcov-report/*
> coverage-results/${coverageDir}")
> reportTitles << "'${it.packageJson.name }'"
> }
> pipelineContext.publishHTML(
> target: [allowMissing : false,
> alwaysLinkToLastBuild: true,
> keepAll : true,
> reportDir : 'coverage-results/**/*',
> reportFiles : 'index.html',
> includes : '**/*,**/**/*',
> reportName : 'Jest Coverage',
> reportTitles : reportTitles.join(',')]
> )
> The issue I'm having is that for some reason, it's not seeing the folder,
> I guess?
> ERROR: Specified HTML directory
> '/home/rh/workspace/ckages_task_test-jest-publishing/coverage-results/**/*'
> does not exist.
>
> I went into our build node and checked, and that directory does exist, so
> I'm unsure where my issue lies.
>
> Thanks,
> Steve
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/53090af4-a733-448e-b9fc-d78a36436817n%40googlegroups.com
> 
> .
>

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

Re: Git Additional Behaviors potential bug

[Mark Waite]

On Mon, Aug 24, 2020 at 5:29 PM John Patrick  wrote:

> Might be a question for developers or a bug ticket.
>
> I've got a multibranchPipelineJob project which runs a Jenkinsfile. The
> job executes as expected apart form one part.
>
> If I select "Configure remote name" and change it to "origin1". When I do
> "sh 'git remote -v'". I see as expected;
>
> [Pipeline] sh
>  +
> git remote -v
> origin1 REPO (fetch)
> origin1 REPO (push)
> [Pipeline] sh
>
> But If I do "Custom user name/e-mail address" and enter say "aName" and
> "aem...@example.tld". When I do "sh 'git config --list'". I don't see
> user.name or user.email set, I just see;
>
> [Pipeline] sh
>  +
> git config --list
> core.repositoryformatversion=0
> core.filemode=true
> core.bare=false
> core.logallrefupdates=true
> remote.origin1.url=REPO
> remote.origin1.fetch=+refs/heads/*:refs/remotes/origin1/*
> [Pipeline] sh
>
> According to the documentation I should be seeing user.name and
> user.email set here. Just wondering if it's a bug, a bug with multibranch
> pipeline job, or I'm missing a step in my Jenkinsfile.
>
>
It is a bug in the documentation.  The documentation say one thing (sets
config) while the code does something better (sets the environment variable
GIT_COMMITTER_NAME and GIT_AUTHOR_NAME).  Documentation fix was merged
today and should be visible within the next 24 hours at
https://plugins.jenkins.io/git/#custom-user-name-e-mail-address

Mark Waite

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

Re: Clean up Jenkins Setup using legacy Workspace Root Directory

[the.n...@gmail.com]

I'd like to bump this. We have the same situation and would like a 
procedure to move to a new workspace structure.

On Friday, May 3, 2019 at 7:15:15 a.m. UTC-4 Saffu wrote:

> Hi All,
>
> Can anyone advise me the steps what to do about this Jenkins build 
> node console message please?
>
> Apr 15 08:00:06 q4de3gsy751 jenkins[26061]: WARNING: JENKINS-34564 path 
> sanitization ineffective when using legacy Workspace Root Directory 
> _${ITEM_ROOTDIR}/workspace_; switch to 
> ${JENKINS_HOME}/workspace/${ITEM_FULLNAME} as in JENKINS-8446 / 
> JENKINS-21942
> /var/log/jenkins/jenkins.log-20190416.gz:Apr 15 08:00:08 q4de3gsy751 
> jenkins[26061]: WARNING: JENKINS-34564 path sanitization ineffective when 
> using legacy Workspace Root Directory _${ITEM_ROOTDIR}/workspace_; switch 
> to ${JENKINS_HOME}/workspace/${ITEM_FULLNAME} as in JENKINS-8446 / 
> JENKINS-21942
> /var/log/jenkins/jenkins.log-20190416.gz:Apr 15 08:00:09 q4de3gsy751 
> jenkins[26061]: WARNING: JENKINS-34564 path sanitization ineffective when 
> using legacy Workspace Root Directory _${ITEM_ROOTDIR}/workspace_; switch 
> to ${JENKINS_HOME}/workspace/${ITEM_FULLNAME} as in JENKINS-8446 / 
> JENKINS-21942
>
>
> Thanks in advance.
>
>
> Regards,
> Sarfroz
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3042564c-33c4-4575-ac58-3fca20a27ce2n%40googlegroups.com.

Git Additional Behaviors potential bug

[John Patrick]

Might be a question for developers or a bug ticket.

I've got a multibranchPipelineJob project which runs a Jenkinsfile. The job 
executes as expected apart form one part.

If I select "Configure remote name" and change it to "origin1". When I do 
"sh 'git remote -v'". I see as expected;

[Pipeline] sh 
 +
git remote -v
origin1 REPO (fetch)
origin1 REPO (push)
[Pipeline] sh

But If I do "Custom user name/e-mail address" and enter say "aName" and 
"aem...@example.tld". When I do "sh 'git config --list'". I don't see 
user.name or user.email set, I just see;

[Pipeline] sh 
 +
git config --list
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
remote.origin1.url=REPO
remote.origin1.fetch=+refs/heads/*:refs/remotes/origin1/*
[Pipeline] sh

According to the documentation I should be seeing user.name and user.email 
set here. Just wondering if it's a bug, a bug with multibranch pipeline 
job, or I'm missing a step in my Jenkinsfile.

I'm using a Scripts Pipeline Jenkinsfile and am checking out the code using 
"checkout scm". And I've checked user.name and user.email before and after 
checkout.

Anyone else using multibranchPipelineJob and Custom name and email?

I've tested on v2.204.6, v2.222.4 and v.235.5, and the latest plugins which 
install on each of those versions.

Cheers,
John

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a632cc2f-c586-42ca-9f36-b6699631a9dfn%40googlegroups.com.

[Event] DevOps World | Sept 22-24: Jenkins volunteers needed

[Alyssa Tong]

Hi All,

The Jenkins project, along with CDF  will be at DevOps
World's virtual event  this coming
Sept 22-24, 2020. We are looking for Jenkins volunteers to help staff the
virtual booth, it is a 1 hour commitment in the comfort of your home/office
- of course we would not decline if you'd like to give more than 1 hr ☺.
Duties include answering Jenkins technical questions by attendee(s). The
signup sheet is  HERE

.

If you have questions pls reach out.

Thank you,
alyssa

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

HTML Publisher pipeline syntax

[Steven Heuertz]

Hi,

I'm working with a pipeline that builds a bunch of npm packages in a 
monorepo. Our commands are run on each package individually, so we have 
individual test/lint results in each package. I'm trying to pull all of the 
results into a single html report. To make this easier, I'm copying the 
reports into a central folder, and trying to build the report from there:
pipelineContext.echo "Publishing jest results"
pipelineContext.sh(script: 'mkdir coverage-results')
List reportTitles = []
changeSet.each {
String coverageDir = it.packageJson.name.replace('/', '_')
pipelineContext.sh(script: "mkdir -p coverage-results/${coverageDir}")
pipelineContext.sh(script: "cp -R ${it.path}/coverage/lcov-report/* 
coverage-results/${coverageDir}")
reportTitles << "'${it.packageJson.name }'"
}
pipelineContext.publishHTML(
target: [allowMissing : false,
alwaysLinkToLastBuild: true,
keepAll : true,
reportDir : 'coverage-results/**/*',
reportFiles : 'index.html',
includes : '**/*,**/**/*',
reportName : 'Jest Coverage',
reportTitles : reportTitles.join(',')]
)
The issue I'm having is that for some reason, it's not seeing the folder, I 
guess?
ERROR: Specified HTML directory 
'/home/rh/workspace/ckages_task_test-jest-publishing/coverage-results/**/*' 
does not exist.

I went into our build node and checked, and that directory does exist, so 
I'm unsure where my issue lies.

Thanks,
Steve

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/53090af4-a733-448e-b9fc-d78a36436817n%40googlegroups.com.

Re: ExcludedRegions for SVN not working in Pipeline

[Fabian Cenedese]

>I have a pipeline which is configured for the SVN path in Jenkins pipeline. 
>https://svn.domain.com/org/project/trunk/Platform/Src
>
>Within Src, I have a Build folder and there are some projects inside that as 
>well. So, I want to exclude some projects within the Build folder. So I put 
>the ExcludedRegions like /Build/ProjectFolder1/.* and so on. But this is not 
>working. Any help will be appreciated.

Depending on the number of projects to include/exclude you could create
a new svn "repository" which just consists of external links to the stuff
you want and checkout that. However depending on your structure
this might not be feasible.

bye  Fabi

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20200824172418.F127141B9BC8%40macserver.private.

Re: Security Vulnerability on my Jenkins Server

[Ivan Fernandez Calvo]

Yes, configuring the ciphers accepted by your JDK edit the 
file lib\security\java.security (the path will vary based on your Java 
version)

El lunes, 24 de agosto de 2020 a las 16:48:22 UTC+2, eric@gmail.com 
escribió:

> Hi all!  I'm getting hit by my secuity team for a vulnerability for the 
> Jenkins CLI via ssh allowing the following weak ciphers:
>
>   hmac-md5
>   hmac-md5-96
>   hmac-sha1-96
>
> Is there a way to configure ciphers accepted for the Jenkins CLI?
>
> Thanks,
> Eric
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f28c34c0-ad6a-4305-89c5-9fd93f9ffb90n%40googlegroups.com.

Re: ExcludedRegions for SVN not working in Pipeline

[Ven H]

Has anyone faced this? Does anyone have any idea? Please help.

Regards,
Venkatesh


On Fri, Aug 21, 2020 at 12:05 AM Ven H  wrote:

> Does anyone have a solution for this?
>
>
> Regards,
> Venkatesh
>
>
> On Thu, Aug 13, 2020 at 12:00 PM Ven H  wrote:
>
>> Hi,
>>
>> I have a pipeline which is configured for the SVN path in Jenkins
>> pipeline. https://svn.domain.com/org/project/trunk/Platform/Src
>>
>> Within Src, I have a Build folder and there are some projects inside that
>> as well. So, I want to exclude some projects within the Build folder. So I
>> put the ExcludedRegions like */Build/ProjectFolder1/.** and so on. But
>> this is not working. Any help will be appreciated.
>>
>> Regards,
>> Venkatesh
>>
>

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

Security Vulnerability on my Jenkins Server

[eric....@gmail.com]

Hi all!  I'm getting hit by my secuity team for a vulnerability for the 
Jenkins CLI via ssh allowing the following weak ciphers:

  hmac-md5
  hmac-md5-96
  hmac-sha1-96

Is there a way to configure ciphers accepted for the Jenkins CLI?

Thanks,
Eric

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/392ef479-9516-4f17-9373-8054ef703bb5n%40googlegroups.com.

Re: [Gerrit-Trigger Plugin] Unable to connect successfully to our Gerrit server via the REST API

['Björn Pedersen' via Jenkins Users]

Hi,

the gerrit-trigger-plugin requires ssh access ( stream-events is only 
available via ssh in a standard setup).  Check the gerrit code review 
plugin (https://plugins.jenkins.io/gerrit-code-review/) if  
you  don't need stream events triggering.


Björn

bbr...@ucdavis.edu schrieb am Sonntag, 23. August 2020 um 06:24:40 UTC+2:

> I'm sorry for trying to revive this, but I didn't receive any answers from 
> my initial posting.
>
> I'm still currently blocked on this and some assistance, if possible, 
> would be greatly appreciated.
>
> Kind regards,
> Bobby
>
> On Friday, August 14, 2020 at 5:55:56 AM UTC-7 Bobby Bruce wrote:
>
>>
>> Dear all,
>>
>> We are currently in the process of setting up a Jenkins server to listen 
>> and respond to events on our Gerrit code review system. As such, we are 
>> using the "Gerrit-Trigger" plugin. A small problem is that those running 
>> our Gerrit server will not give us SSH access. We therefore have to rely 
>> solely on Gerrit's REST API. We have a HTTP username and password setup 
>> which we have verified is correct and has adequate permissions.
>>
>> When adding the Gerrit server to the Gerrit-Trigger server list we add 
>> the frontend URL and, in the advanced section, select "Use REST API"  then 
>> enter our Gerrit HTTP Username and Password. Upon clicking "Test REST 
>> Connect" we receive the "Success" message. I have confirmed that we receive 
>> an error message when entering the wrong username and password, so I assume 
>> the Gerrit-Trigger plugin is able to make some kind of connection. When 
>> saving and leaving the configuration page we try to start the 
>> Gerrit-Trigger server by pressing the red button on the Gerrit-Trigger 
>> dashboard. The button blinks for a few seconds then stops. Looking into the 
>> Jenkins log, the following is given:
>>
>> `2020-08-14 04:26:35.693+ [id=37] INFO c.s.h.p.g.t.
>> GerritProjectListUpdater#tryLoadProjectList: Not connected to 
>> gem5-review, waiting for 64 second(s)`
>>
>> The only theory we have right now is that perhaps the Gerrit-Trigger 
>> plugin requires SSH access as a prerequisite. We can't find this explicitly 
>> noted anywhere, and we don't know why this would be the case given the 
>> plugin has the access it requires via the REST API. If this is the case, 
>> it'd be nice if someone could verify this for us. If not, we would 
>> appreciate some help with this issue.
>>
>> Attached is our gerrit-trigger.xml configuration file (passwords 
>> redacted).
>>
>> Jenkins Version: 2.235.2
>> Gerrit Trigger Version: 2.30.5
>> Gerrit Code Review Version: 3.2.3-1238-g443f7314cb
>>
>> Thank you very much for your time.
>>
>> Kind regards,
>> Bobby
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/acc0fa90-c587-463b-9de2-cf4f57a8d7f0n%40googlegroups.com.