Closed brunourb closed 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
Hi,
The command openshift.newApp in Jenkins pipeline not create deploymentconfig (DC). I have 2 jenkins (test and staging) with the same image in quay.io and same plugin version.
Quay.io repo: https://quay.io/repository/openshift/origin-jenkins/, tag is 4.6 Jenkins version is: 2.222.1-1.1
I tested the OpenShift Jenkins Pipeline version 1.0.32 at 1.0.34. https://updates.jenkins.io/download/plugins/openshift-client/
In TEST, the version of oc client and k8s is:
TEST
In stage, the version of oc client and k8s is:
STAGING
When i run the pipeline with this stage, the DC is not create in STAGING environment. In DEV environment the dc is created.
Console the TEST environment
Console in the STAGING environment
When i type command oc get all in the DEV project, console returns:
oc get all in the STAGING environment
DEBUG openshift.verbose() in TEST
DEBUG openshift.verbose() in STAGING
who can create deploymentconfig in STAGING
I don't understand why newApp not create the deploymentconfig. Anybody can help me? Regards