This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Context:
We are trying to develop an automatic lifecycle for our deployment processes in UrbanCode Deploy 7.3.2
Problem:
We get the error "IO error: direct console access unavailable" when trying to update the processes in UCD from a Jenkins pipeline.
Steps to reproduce:
1) Download the PACC binaries from the UCD server embedded tools
2) Run the upload-application-process script inside a Jenkins sh statement
Here is an example of the upload-component-process script:
#!/bin/bash
PACC_LOCATION=`dirname "$0"`
PACC_PROGRAM=`basename "$0"`
if [ "$PACC_LOCATION" = "." ]; then
PACC_LOCATION=`pwd`
fi
exec java \
"-Dpacc.location=$PACC_LOCATION" \
"-Dpacc.program=$PACC_PROGRAM" \
-cp "$PACC_LOCATION/lib/pacc-0.1.0.1112755.jar" \
ucd.pacc.main.UploadComponentProcessMain \
"$@"
If you decompile that JAR file inside the lib directory you can see the class handling the password.
The method throwing the Exception is this one:
protected ConsoleWrapper mustGetConsole() throws IOException {
return (ConsoleWrapper)this.getGlobalProcessState().getConsole().orElseThrow(() -> {
return new IOException("direct console access unavailable");
});
}
Questions & ideas:
Is it possible to improve the password management by the AbstractProcessCommand class in order to avoid a manual interactive prompt?
How do you recommend clients to achieve a lifecycle with the defined processes saved in an external repository? Any recommendations?
It should be great for all if we could run the script outside our local environments.
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you very much for meeting with our team. We will be working to implement this idea for a release later in the year.
Thank you very much for the detailed explanation that you provided. We are going to setup an internal discussion topic with the development team to review. If required, we will be in touch to setup a meeting so our development team can speak directly with you. For now, I think we have what we need and we will be in touch.
Hi All,
I received this information from Bharath which is helpful:
I will add a little context, the customer wants to make changes to UCD processes through GIT. Any changes that they would like to do, they want to first do it in a lower environment before propagating it to PROD UCD. Currently, they would like to modify processes in an editor outside of the UCD process design page, store it in GIT and then upload it to test UCD. If they are satisfied with their change then they would like to upload it to PROD UCD. They want to use PACC in this process as it helps them in modifying processes through editors. They are trying to implement GITOPS with UCD processes.
Their issue was originally raised as a support case (TS015432445) but it was responded with as an unsupported feature and hence the RFE from the customer.
Regards,Bharath
Can you provide a little more context around your Jenkins process? Is this building some code and then as part of the Jenkins build you want to upload the process used in Deploy to a git repository? We are a little confused on our side. Did you make a change to the process in the Jenkins build? We need more context to understand this much better for our development team to address. If it would help to meet, we would be happy to do that as well. Thank you!
Thank you for submitting this idea. We are going to create a discussion topic with our development team to review your comments above. We will be in touch.