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

DAT-15775 #4780

Merged
merged 360 commits into from
Dec 11, 2023
Merged

DAT-15775 #4780

merged 360 commits into from
Dec 11, 2023

Conversation

sayaliM0412
Copy link
Contributor

@sayaliM0412 sayaliM0412 commented Aug 29, 2023

Impact

  • Bug fix (non-breaking change which fixes expected existing functionality)
  • Enhancement/New feature (adds functionality without impacting existing logic)
  • Breaking change (fix or feature that would cause existing functionality to change)
  1. build.yml: removing the use of workflow-helper.js from build.yml
  2. run-tests.yml : consist of unit-tests and integration-tests. If the PR is from a forked repo, only authorize will allow the workflow to run.
  3. new build.yml : build and publishes packages to build artifact page and GPM
  4. functional-tests and tests-harness : are run after the new build.yml completes successfully. The link is visible on the run of run-tests.yml

Description

Things to be aware of

Things to worry about

Additional Context

@sayaliM0412 sayaliM0412 force-pushed the github-action-DAT-15775 branch 2 times, most recently from 776d16d to 53b7302 Compare August 31, 2023 21:17
@sayaliM0412 sayaliM0412 temporarily deployed to internal August 31, 2023 21:27 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal August 31, 2023 21:33 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal August 31, 2023 21:40 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 1, 2023 13:04 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 1, 2023 13:48 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 1, 2023 19:40 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 6, 2023 15:13 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 6, 2023 15:22 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 6, 2023 15:44 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 6, 2023 16:24 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 6, 2023 16:24 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 6, 2023 16:34 — with GitHub Actions Inactive
@sayaliM0412 sayaliM0412 temporarily deployed to internal September 6, 2023 16:39 — with GitHub Actions Inactive
…compareGeneratedSqlWithExpectedSqlForMinimalChangesets/alterSequence/mariadb.sql

Signed-off-by: filipe <flautert@liquibase.org>
…compareGeneratedSqlWithExpectedSqlForMinimalChangesets/createSequence/mariadb.sql

Signed-off-by: filipe <flautert@liquibase.org>
…compareGeneratedSqlWithExpectedSqlForMinimalChangesets/dropSequence/mariadb.sql

Signed-off-by: filipe <flautert@liquibase.org>
…compareGeneratedSqlWithExpectedSqlForMinimalChangesets/renameSequence/mariadb.sql

Signed-off-by: filipe <flautert@liquibase.org>
.github/workflows/build.yml Show resolved Hide resolved
@sayaliM0412 sayaliM0412 merged commit 5afcbc9 into master Dec 11, 2023
58 of 61 checks passed
@sayaliM0412 sayaliM0412 deleted the github-action-DAT-15775 branch December 11, 2023 23:36
Comment on lines +54 to +55
latest_merge_sha=`(git rev-parse HEAD)`
echo "latestMergeSha=${latest_merge_sha}" >> $GITHUB_OUTPUT
Copy link
Contributor

Choose a reason for hiding this comment

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

I wonder if this will get us the sha we are looking for. We've had trouble using this kind of thing in the past, where it gave us commits that didn't exist, but that may have been so long ago that it's not a problem any more, particularly if we used to build with pull_request_target and now we don't (or vice versa). It's something to keep an eye on.

group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
group: ${{ github.workflow }}-${{ github.head_ref && github.ref || github.run_id }}
cancel-in-progress: false
Copy link
Contributor

Choose a reason for hiding this comment

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

Is cancel-in-progress supposed to be false?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I will check on this again. I remember I had to do this for testing.

## verify that the contents of the tar matches the expectation
echo "Comparing the contents of the tar.gz with the expected contents (using baseline file in liquibase-dist directory) to ensure that no new files were accidentally added. A failure here indicates that a new file was added to the tar.gz, and it should either be rectififed or added to the baseline."
#echo "Comparing the contents of the tar.gz with the expected contents (using baseline file in liquibase-dist directory) to ensure that no new files were accidentally added. A failure here indicates that a new file was added to the tar.gz, and it should either be rectififed or added to the baseline."
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggest you uncomment this echo

}
run-functional-tests:
needs: [ setup, build_publish_branch ]
uses: liquibase/liquibase/.github/workflows/run-functional-tests.yml@github-action-DAT-15775
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this line have @github-action-DAT-15775 in it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this was taken care of

Copy link
Contributor

Choose a reason for hiding this comment

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

Should the steps in this workflow be commented out?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The azure uber jar was creating issue during last release as well. I did not want to look into it for this ticket and go down that rabbit hole.

Comment on lines +61 to +66
- name: Report PRO-Tests Run URL
uses: actions/github-script@v6.4.1
with:
script: |
const targetURL = "https://github.com/liquibase/liquibase-pro-tests/actions/runs/${{ steps.return_dispatch.outputs.run_id }}"
core.notice("Pro-Tests Run URL: " + targetURL);
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a great addition, nice job!

Copy link
Contributor

Choose a reason for hiding this comment

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

This is essentially the same exact file as .github/workflows/run-functional-tests.yml and these could probably be combined and made more dynamic.

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.

None yet

4 participants