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.

Sign up for GitHub

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

Jump to bottom

DEV Pipeline #114

Merged
merged 21 commits into from
Apr 3, 2024
Merged

DEV Pipeline #114

merged 21 commits into from
Apr 3, 2024

Conversation

alalvi00
Copy link
Contributor

@alalvi00 alalvi00 commented Mar 22, 2024 •
edited
Loading

Overview/Summary

Created a dev pipeline to be triggered upon release. Right now it will be triggered upon push to main for testing purposes

This PR fixes/adds/changes/removes

  1. Replace me
  2. Replace me
  3. Replace me

Breaking Changes

  1. Replace me
  2. Replace me

Testing Evidence

Please provide any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).

As part of this Pull Request I have

  • Checked for duplicate Pull Requests
  • Associated it with relevant GitHub Issues
  • Ensured my code/branch is up-to-date with the latest changes in the main branch
  • Performed testing and provided evidence.
  • Updated relevant and associated documentation.
  • Ensure PowerShell module versions have been updated (manually or with the ./tools/Update-ModuleVersions.ps1 script)

@alalvi00 alalvi00 requested review from singhgss and dutt0 as code owners March 22, 2024 14:10
@alalvi00
Copy link
Contributor Author

#103

dutt0
dutt0 approved these changes Mar 22, 2024
View reviewed changes
Copy link
Contributor

@dutt0 dutt0 left a comment •
edited
Loading

Choose a reason for hiding this comment

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

It seems that the workflow using push to main branch for workflow testing for now. Approving now so you can test and later update PR with release tag and re-request review. Thanks.

@dutt0 dutt0 linked an issue Mar 22, 2024 that may be closed by this pull request
Create a workflow to update SSC Dev tenant upon release tag #103
Closed
dutt0
dutt0 reviewed Mar 28, 2024
View reviewed changes
Copy link
Contributor

@dutt0 dutt0 left a comment

Choose a reason for hiding this comment

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

Code triggers on 'push' to a branch. Please update it to tag release.

@dutt0 dutt0 self-requested a review March 28, 2024 12:30
@alalvi00
Copy link
Contributor Author

alalvi00 commented Apr 2, 2024

Code triggers on 'push' to a branch. Please update it to tag release.

Yes once it redploy dev env on main branch, I will change it to be triggered on release with a new pr

@alalvi00 alalvi00 requested review from nadersip and removed request for MathesonSho and amrinderssc April 2, 2024 19:39
@alalvi00 alalvi00 merged commit 8a9e36c into main Apr 3, 2024
4 checks passed
@alalvi00 alalvi00 deleted the dev_pipeline_aalvi branch April 3, 2024 14:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dutt0 dutt0 dutt0 approved these changes

@nadersip nadersip nadersip approved these changes

@singhgss singhgss Awaiting requested review from singhgss singhgss is a code owner

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Create a workflow to update SSC Dev tenant upon release tag
3 participants
@alalvi00 @nadersip @dutt0