Skip to content
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

integrationArtifactTransport Command #4131

Merged
merged 15 commits into from
Dec 20, 2022

Conversation

mayurmohan
Copy link
Contributor

Changes

integrationArtifactTransport Command :- Integration artifact content transport using SAP Content Agent service

  • Tests
  • Documentation

@mayurmohan mayurmohan requested a review from a team as a code owner November 21, 2022 05:26
@cla-assistant
Copy link

cla-assistant bot commented Nov 21, 2022

CLA assistant check
All committers have signed the CLA.

Copy link
Contributor

@srinikitha09 srinikitha09 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few typos

documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved

With this step, you can transport SAP Cloud Integration content across various landscapes using SAP Content Agent Service.

SAP Cloud Integration provides content transport mechanism. SAP Content Agent service enables you to assemble the content from these content providers in MTAR format. Later, this content is either available for download or exported to the configured transport queue, such as SAP Cloud Transport Management. For more information on
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you explain just a bit more what you mean by "SAP Cloud Integration provides content transport mechanism."? Do you mean that SAP Cloud Integration is a content provider? (You mention content providers in the next sentence, but which content providers do you mean?)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reverted

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is a separate review happen for documentation part by the Documentation experts, i would suggest not review the .md. .yaml content in detail

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the documentation is my main way (and probably the main way for other people) to understand what this step is supposed to do, I would like a bit more explanation there if you could add that. When will the documentation experts review this? I can wait to add my review until they've made changes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After the documentation review, I'm still left with some questions about what exactly this step does and what the documentation is saying. Could you please elaborate on "SAP Cloud Integration provides content transport mechanism." Is there any other documentation you could link here? Also you mention content providers in the next sentence, but which content providers do you mean?

Since I'm not a Integration Suite expert, my suggestions won't be completely accurate. @AnnikaGonnermann and @axelalbrechtsap maybe you could support here with adding more detail to the documentation from the point of view of Integration Suite? I think it should be written for someone that has no idea what this step should do.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 points:

  1. "SAP Cloud Integration provides content transport mechanism" used in the already referred public documentation which we also used as is (https://help.sap.com/docs/CONTENT_AGENT_SERVICE/ae1a4f2d150d468d9ff56e13f9898e07/8e274fdd41da45a69ff919c0af8c6127.html)
  2. there is blog linked in the last step which provide step by step instruction how to do integration package transport with CAS, TMS (https://blogs.sap.com/2022/03/25/transport-sap-cloud-integration-ci-cpi-content-with-transport-management-service-tms-and-content-agent-service-cas/)

i feel this is good enough from documentation standpoint.

documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
cmd/integrationArtifactTransport_test.go Outdated Show resolved Hide resolved
cmd/integrationArtifactTransport_test.go Outdated Show resolved Hide resolved
cmd/integrationArtifactTransport_test.go Outdated Show resolved Hide resolved
cmd/integrationArtifactTransport_test.go Outdated Show resolved Hide resolved
cmd/integrationArtifactTransport.go Outdated Show resolved Hide resolved
Copy link
Member

@LindaSieb LindaSieb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since I'm not sure how to test this, could you please upload some sort of evidence that it worked properly? A screenshot of logs maybe? (of course without any sensitive information)

@mayurmohan
Copy link
Contributor Author

mayurmohan commented Dec 7, 2022

Since I'm not sure how to test this, could you please upload some sort of evidence that it worked properly? A screenshot of logs maybe? (of course without any sensitive information)
please refer below details:

Jenkins Job Log:
transportJob

TMSLog:
TMSTrace

TMSQueue :

TMSQueue

Logs:
consoleText.txt

Copy link
Member

@LindaSieb LindaSieb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documentation suggestions. Please let me know if I've misunderstood the step 🙂

documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
resources/metadata/integrationArtifactTransport.yaml Outdated Show resolved Hide resolved
resources/metadata/integrationArtifactTransport.yaml Outdated Show resolved Hide resolved
documentation/docs/steps/integrationArtifactTransport.md Outdated Show resolved Hide resolved
Copy link
Member

@LindaSieb LindaSieb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mayurmohan! 🙂

@LindaSieb
Copy link
Member

/it

1 similar comment
@LindaSieb
Copy link
Member

/it

@LindaSieb
Copy link
Member

CLA assistant check Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 4 committers have signed the CLA.✅ mayurmohan✅ LindaSieb❌ I050368❌ srinikitha09

I050368 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@I050368 and @srinikitha09 could you sign the license agreement?

@LindaSieb
Copy link
Member

@I050368 and @srinikitha09 could you sign the license agreement?

@mayurmohan are you I050368? It looks like some tests are failing because "I050368" hasn't signed the license agreement

@LindaSieb
Copy link
Member

LindaSieb commented Dec 20, 2022

@I050368 and @srinikitha09 could you sign the license agreement?

@mayurmohan are you I050368? It looks like some tests are failing because "I050368" hasn't signed the license agreement

"I050368 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account."

@LindaSieb
Copy link
Member

/it

@LindaSieb LindaSieb force-pushed the integrationArtifactTransport branch from 860f804 to e6803cb Compare December 20, 2022 10:53
@LindaSieb LindaSieb requested review from inf2381 and a team as code owners December 20, 2022 10:53
@LindaSieb LindaSieb force-pushed the integrationArtifactTransport branch from e6803cb to c547de5 Compare December 20, 2022 10:55
@LindaSieb
Copy link
Member

/it

@LindaSieb LindaSieb enabled auto-merge (squash) December 20, 2022 11:05
@LindaSieb LindaSieb merged commit a65df9c into SAP:master Dec 20, 2022
maxatsap pushed a commit to maxatsap/jenkins-library that referenced this pull request Jul 23, 2024
* integrationArtifactTransport Command

* CodeReview Fix

* CodeReview Fix

* codereview fix

* Update documentation/docs/steps/integrationArtifactTransport.md

Co-authored-by: Srinikitha Kondreddy <[email protected]>

* Update documentation/docs/steps/integrationArtifactTransport.md

Co-authored-by: Srinikitha Kondreddy <[email protected]>

* CodeReview Fixes

* CodeReview FIxes

* CodeReview Fix

* Doc Fixes

* Update documentation/docs/steps/integrationArtifactTransport.md

Co-authored-by: Linda Siebert <[email protected]>

* Doc fixes

* Doc Fixes

* CodeReview Fixes

* Doc Fixes

Co-authored-by: Linda Siebert <[email protected]>
Co-authored-by: Srinikitha Kondreddy <[email protected]>
Co-authored-by: Linda Siebert <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants