Re: step in build suddenly injecting new parameter flags, resulting in build failure

[Glenn Caccia]

Unfortunately, no.  The POM and project are in source control.  No 
changes.  The maven plugin axistools is a very old plugin that hasn't had a 
new version since 10 years ago.  Plus, if I build the project directly 
through maven locally, it builds fine without the additional parameters 
that I see when running it through Jenkins.

On Saturday, February 15, 2020 at 2:42:07 AM UTC-8, James Nord wrote:
>
> Could it be that you have not locked the versions of maven plugins in your 
> maven pom.xml?
>
> the axis-maven-plugin or whatever you are using to generate the wsdl 
> that's failing could have been updated and you may be getting a newer 
> version than you used to in the CO environment.
> https://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html
>

-- 
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/723a3bab-518c-4ab7-bd30-0405d725f4f1%40googlegroups.com.

Re: step in build suddenly injecting new parameter flags, resulting in build failure

[Glenn Caccia]

I also uninstalled or downgraded all the others in that list of plugins 
except for workflow-cps (no option to do either for that) and restarted and 
still no good.

On Thursday, February 13, 2020 at 3:47:12 PM UTC-8, Glenn Caccia wrote:
>
> I have a Jenkins project that runs a maven build.  The maven build 
> includes a step where it uses axistools, maven goal wsdl2java, to build 
> classes from a soap service endpoint. This has been working fine for the 
> past few years. The last good build was from 1/31. On 2/4 I tried to build 
> this same project and suddenly that step was failing. I noticed that the 
> step is now including new parameters that were not present before. In the 
> last good build, I see a step like this.. [DEBUG] argslist: [-o, 
> /var/lib/jenkins/jobs/xxx/workspace/target/generated-sources/java, -w, -T, 
> 1.1, 
> file:/var/lib/jenkins/jobs/xxx/workspace/target/axistools/wsdl2java/urlDownloads/http---xxx.xxx.com-8080-xxx-wsdl.wsdl]
>  
> But now, with the builds that are failing, I see this... [DEBUG] 
> argslist: [-o, 
> /var/lib/jenkins/jobs/xxx/workspace/target/generated-sources/java, -w, -T, 
> 1.1, -U, , -P, , 
> file:/var/lib/jenkins/jobs/xxx/workspace/target/axistools/wsdl2java/urlDownloads/http---xxx.xxx.com-8080-xxx-wsdl.wsdl]
>  So 
> something is injecting -U, , -P, ,. I looked at what plugins had been 
> recently updated and found the following... 
> config-file-provider
> github-branch-source
> script-security
> workflow-cps
> subversion
> The script-security plugin seemed like a likely suspect and I downgraded 
> it and restarted Jenkins, but still get same issue. Config-file-provider 
> does not provide a downgrade option. Any thoughts? 
>

-- 
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/30f369cf-2a77-455c-ab26-375ff9725db1%40googlegroups.com.

step in build suddenly injecting new parameter flags, resulting in build failure

[Glenn Caccia]

I have a Jenkins project that runs a maven build.  The maven build includes 
a step where it uses axistools, maven goal wsdl2java, to build classes from 
a soap service endpoint. This has been working fine for the past few years. 
The last good build was from 1/31. On 2/4 I tried to build this same 
project and suddenly that step was failing. I noticed that the step is now 
including new parameters that were not present before. In the last good 
build, I see a step like this.. [DEBUG] argslist: [-o, 
/var/lib/jenkins/jobs/xxx/workspace/target/generated-sources/java, -w, -T, 
1.1, 
file:/var/lib/jenkins/jobs/xxx/workspace/target/axistools/wsdl2java/urlDownloads/http---xxx.xxx.com-8080-xxx-wsdl.wsdl]
 
But now, with the builds that are failing, I see this... [DEBUG] argslist: 
[-o, /var/lib/jenkins/jobs/xxx/workspace/target/generated-sources/java, -w, 
-T, 1.1, -U, , -P, , 
file:/var/lib/jenkins/jobs/xxx/workspace/target/axistools/wsdl2java/urlDownloads/http---xxx.xxx.com-8080-xxx-wsdl.wsdl]
 So 
something is injecting -U, , -P, ,. I looked at what plugins had been 
recently updated and found the following... 
config-file-provider
github-branch-source
script-security
workflow-cps
subversion
The script-security plugin seemed like a likely suspect and I downgraded it 
and restarted Jenkins, but still get same issue. Config-file-provider does 
not provide a downgrade option. Any thoughts? 

-- 
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/1b0e6acc-359a-46f5-a927-ff5678d0cb9a%40googlegroups.com.

Re: Error following installation steps for Jenkins

[Glenn Caccia]

Actually resolved the issue.  I used wget to download the key locally and 
then was able to import.  When using wget, had to use the flag to not check 
certificate...

ERROR: cannot verify jenkins-ci.org's certificate, issued by `/C=US/O=Let's 
Encrypt/CN=Let's Encrypt Authority X3':
  Unable to locally verify the issuer's authority.
ERROR: certificate common name `accounts.jenkins.io' doesn't match 
requested host name `jenkins-ci.org'.
To connect to jenkins-ci.org insecurely, use `--no-check-certificate'.

-- 
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/498bdbbd-a0f5-4eef-9d77-f945974f1438%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Error following installation steps for Jenkins

[Glenn Caccia]

I'm trying to install 2.7.1 LTS on a CentOS 5.6 box.  I'm following the 
instructions for "*Installing Jenkins on Red Hat distributions* 
",
 
which states the following...

sudo wget -O /etc/yum.repos.d/jenkins.repo 
*http://pkg.jenkins-ci.org/redhat-stable/jenkins.repo* 

- sudo rpm --import *https://jenkins-ci.org/redhat/jenkins-ci.org.key* 

- sudo yum install jenkins

The first command works fine, but the second command to import fails...

error: https://jenkins-ci.org/redhat/jenkins-ci.org.key: import read 
failed(-1).

Any thoughts on what I need to do to fix this?


-- 
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/10d56312-2702-43c0-84e5-9adb1c914ea2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.