> [Pipeline] }
> [Pipeline] // node
> [Pipeline] End of Pipeline
> ERROR: script returned exit code 1
> Finished: FAILURE
On Thursday, March 8, 2018 at 11:17:10 AM UTC-6, Joe Cavanaugh wrote:
>
> Yep - the middle section of the first post is when I ran directly as the
>
:31:45 AM UTC-6, slide wrote:
>
> Have you tried running the same command in powershell directly to see if
> the behavior is just powershell itself?
>
> On Thu, Mar 8, 2018 at 8:20 AM Joe Cavanaugh <joe.d.cava...@gmail.com
> > wrote:
>
>> bat 'yarn install' works f
bat 'yarn install' works fine. It seems that the powershell key word does
not work correctly in declarative pipelines consistently.
On Thursday, March 8, 2018 at 9:02:38 AM UTC-6, Joe Cavanaugh wrote:
>
> I didn't post the error message :
>
> ERROR: script returned exit code
I didn't post the error message :
ERROR: script returned exit code 1
Finished: FAILURE
On Wednesday, March 7, 2018 at 4:51:41 PM UTC-6, Joe Cavanaugh wrote:
>
> stage('Build') {
> steps {
> powershell '''
> Write-Output "S
stage('Build') {
steps {
powershell '''
Write-Output "Starting Yarn Install"
try {
\$ErrorActionPreference = 'Stop'
yarn install
} catch {
Write-Output "Install failed : \$PSItem"
You have to have the declarative pipeline 1.2 or higher to do this. I am
having issues putting the "powershell" keyword in the library... otherwise
it seems to work.
On Thursday, January 11, 2018 at 1:41:50 AM UTC-6, Idan Adar wrote:
>
> Indeed possible. See blog post:
>
Anyone else encountering this issue?
--
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
I can now confirm the standard bat 'echo Hello World' works fine - it is
just the powershell keyword that is an issue.
--
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
Forgot to mention - the version of Jenkins is 2.98 with all the latest and
greatest plugin versions (I just updated yesterday 12/28/2017). It is a
windows master build machine running powershell 3.0 and I haven't tested on
a powershell 5.1 machine yet.
--
You received this message because
Set up :
1) Create a Pipeline script in a groovy file such as in the blog
post
https://jenkins.io/blog/2017/10/02/pipeline-templates-with-shared-libraries/
. I called mine dotNetApiPipeline.groovy and saved it to /vars.
> def call(body) {
> // evaluate the body block, and collect
Note - To make what Colin did work, you must be using declarative pipeline
1.2 or higher which has its own list of dependencies. I didn't realize this
right away.
On Monday, October 16, 2017 at 12:03:26 PM UTC-5, Colin Bennett wrote:
>
> The workaround of use the 'tool' function in the
Agree with Devin above, and would highly suggest against setting up the
Master Jenkins server and Sonarqube together - I ran into scaling problems
rather quickly (like within 6 months as people got wind of the Jenkins and
Sonar servers). Migrating Jenkins is pretty easy though, so for the
I don't know if I fully understand your question... but here is something I
did to solve getting scripts for execution in RepoA from repo's B,C,D... I
now know the specific directories to execute the scripts from and the files
that needed to be updated for Puppet.
If you find a better way or
I've used a modified version of the scripts found on
https://support.cloudbees.com/hc/en-us/articles/217630098-How-to-access-Changelogs-in-a-Pipeline-Job-
to great success by putting them as @NonCPS on the bottom of my declarative
pipeline. Just recently I have moved the script to a global
step([
$class: 'XUnitBuilder', testTimeMargin: '3000', thresholdMode: 1,
thresholds: [
[$class: 'FailedThreshold', failureNewThreshold: '', failureThreshold: '0',
unstableNewThreshold: '', unstableThreshold: ''],
[$class: 'SkippedThreshold', failureNewThreshold: '', failureThreshold: '',
15 matches
Mail list logo
