[JIRA] (JENKINS-38483) Pipeline Support: Prepare an environment for the run using Properties File is not working in Pipeline

31 views
Skip to first unread message

o.v.nenashev@gmail.com (JIRA)

unread,
Feb 27, 2017, 8:57:03 AM2/27/17
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
 
Jenkins / Improvement JENKINS-38483
Pipeline Support: Prepare an environment for the run using Properties File is not working in Pipeline
Change By: Oleg Nenashev
Summary: Pipeline Support: Prepare an environment for the run using Properties File is not working in Pipeline
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

o.v.nenashev@gmail.com (JIRA)

unread,
Feb 27, 2017, 8:57:03 AM2/27/17
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: pipeline

o.v.nenashev@gmail.com (JIRA)

unread,
Feb 27, 2017, 9:08:02 AM2/27/17
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on Improvement JENKINS-38483
 
Re: Pipeline Support: Prepare an environment for the run using Properties File is not working in Pipeline

Converting it to RFE since EnvInject does not support Pipeline now (and does not claim to do so)

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 9, 2017, 5:03:01 AM3/9/17
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue

Created an EPIC for it
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 4, 2018, 6:11:07 PM3/4/18
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Unassigned
Change By: Oleg Nenashev
Assignee: Oleg Nenashev

svanoort@cloudbees.com (JIRA)

unread,
Apr 12, 2018, 11:34:06 AM4/12/18
to jenkinsc...@googlegroups.com
Sam Van Oort updated an issue
Change By: Sam Van Oort
Priority: Critical Minor

svanoort@cloudbees.com (JIRA)

unread,
Apr 12, 2018, 11:34:06 AM4/12/18
to jenkinsc...@googlegroups.com
Sam Van Oort commented on Improvement JENKINS-38483
 
Re: Pipeline Support: Prepare an environment for the run using Properties File is not working in Pipeline

Reducing priority to reflect that there's a way to do this and the impact is now smaller.

caryyu.tg@gmail.com (JIRA)

unread,
Mar 4, 2020, 3:53:04 AM3/4/20
to jenkinsc...@googlegroups.com
github.com/caryyu updated an issue
 
Change By: github.com/caryyu
Attachment: screenshot-1.png
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

caryyu.tg@gmail.com (JIRA)

unread,
Mar 4, 2020, 3:57:04 AM3/4/20
to jenkinsc...@googlegroups.com
github.com/caryyu commented on Improvement JENKINS-38483
 
Re: Pipeline Support: Prepare an environment for the run using Properties File is not working in Pipeline

My properties file looks this:
/secret/secrets.properties

VERSION = 12

I can 100% ensure there is a this file in my slave node that is managed by the Kubernetes plugin, which means, every trigger will start an entirely new slave node in place

Here's how my Jenkinsfile looks like:

pipeline {
    stages {
        stage("Hello") {
            steps {
                sh '''
                    pwd
                    echo "Hello World"
                    ls /secret
                    echo "The latest version is: ${VERSION}"
                '''
            }
        }
    }
}

caryyu.tg@gmail.com (JIRA)

unread,
Mar 4, 2020, 3:58:09 AM3/4/20
to jenkinsc...@googlegroups.com
github.com/caryyu edited a comment on Improvement JENKINS-38483
*This is a global configuration setup:*

!screenshot-1.png|thumbnail!

*My properties file looks like this:*
+/secret/secrets.properties+
{code:java}
VERSION = 12
{code}

I can 100% ensure there is a this file in my slave node that is managed by the Kubernetes plugin, which means, every trigger will start an entirely new slave node in place

*Here's how my Jenkinsfile looks like:*
{code:java}

pipeline {
    stages {
        stage("Hello") {
            steps {
                sh '''
                    pwd
                    echo "Hello World"
                    ls /secret
                    echo "The latest version is: ${VERSION}"
                '''
            }
        }
    }
}
{code}

*the output is nothing*

caryyu.tg@gmail.com (JIRA)

unread,
Mar 4, 2020, 3:58:09 AM3/4/20
to jenkinsc...@googlegroups.com
github.com/caryyu edited a comment on Improvement JENKINS-38483
*This is a global configuration setup:*

 !screenshot-1.png|thumbnail!


*My properties file looks this:*
+/secret/secrets.properties+

 {code:java}
VERSION = 12
{code}
I can 100% ensure there is a this file in my slave node that is managed by the Kubernetes plugin, which means, every trigger will start an entirely new slave node in place
*Here's how my Jenkinsfile looks like:*
{code:java}
pipeline {
    stages {
        stage("Hello") {
            steps {
                sh '''
                    pwd
                    echo "Hello World"
                    ls /secret
                    echo "The latest version is: ${VERSION}"
                '''
            }
        }
    }
}
{code}


caryyu.tg@gmail.com (JIRA)

unread,
Mar 4, 2020, 3:59:03 AM3/4/20
to jenkinsc...@googlegroups.com
github.com/caryyu edited a comment on Improvement JENKINS-38483
*This is a global configuration setup:*

!screenshot-1.png|thumbnail!

*My properties file looks like this:*

+/secret/secrets.properties+
{code:java}
VERSION = 12
{code}
I can 100% ensure there is a this file in my slave node that is managed by the Kubernetes plugin, which means, every trigger will start an entirely new slave node in place

*Here's how my Jenkinsfile looks like:*
{code:java}
pipeline {
    stages {
        stage("Hello") {
            steps {
                sh '''
                    pwd
                    echo "Hello World"
                    ls /secret
                    echo "The latest version is: ${VERSION}"
                '''
            }
        }
    }
}
{code}

* conclusion: !!!! the output is nothing !!! *

jglick@cloudbees.com (JIRA)

unread,
Mar 4, 2020, 4:55:03 PM3/4/20
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 
Change By: Jesse Glick
Component/s: pipeline
Reply all
Reply to author
Forward
0 new messages