-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User/muzikovam/zowe yaml diff #3998
Conversation
doing sed of properties file via JCL Signed-off-by: mm667937 <[email protected]>
…alid Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
download final zowe.yaml Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
…there because of permissions that the end user will have to solve, we don't need to) Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
temporarily save files Signed-off-by: Marketka <[email protected]>
Signed-off-by: mm667937 <[email protected]>
… it with newlines Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
…e/zowe-install-packaging into user/muzikovam/zoweYamlDiff
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
…kflow output and then comparing that diff to diff that is output on "live" example and wf output Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Test workflow 5424 is started. |
, SMPE, PSWI build 6090 SUCCEEDED. |
Test workflow 5425 is started. |
We agreed to separate the ZWECONF yaml test so it can run everytime. I will also try to delete private info from said test. So I am closing this PR for now. |
…hope Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
…with runtimeDirectory Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
Signed-off-by: mm667937 <[email protected]>
build 6116 SUCCEEDED. |
build 6117 SUCCEEDED. |
Test workflow 5440 is started. |
Test workflow 5441 is started. |
Signed-off-by: MarkAckert <[email protected]>
build 6119 SUCCEEDED. |
Test workflow 5443 is started. |
@muzikovam I split the PSWI YAML check into a new workflow, and will test it after it's merged into staging. Please let me know if this PR needs to make the 3.0.0 release. |
Please check if your PR fulfills the following requirements. This is simply a reminder of what we are going to look for before merging your PR. If you don't know all of this information when you create this PR, don't worry. You can edit this template as you're working on it.
PR type
What type of changes does your PR introduce to Zowe? Put an
x
in the box that applies to this PR. If you're unsure about any of them, don't hesitate to ask.Relevant issues
Fixes
Changes proposed in this PR
Does this PR introduce a breaking change?
Does this PR do something the person installing Zowe should know about?
Just tests for yaml generated by ZWECONF workflow so that zowe.yaml produced by ZWECONF workflow has the same variables as zowe-example.yaml.
Is there a related doc issue or Pull Request?
Doc issue/PR number:
Other information