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

Add Bitbucket support #71

Merged
merged 4 commits into from
Jun 19, 2022

Conversation

quarenw
Copy link
Contributor

@quarenw quarenw commented May 31, 2022

This PR adds support to install packages from Bitbucket both public and private only using Basic auth.

Tests added for inexistant packages and public package. The package used in the public test is from Atlassian but is quite big and takes a long time to run the test. Was not able to find a better package hosted on Bitbucket which is reliable and immediately usable for use in the test.

Private repos is tested and working but as with Github it has not been added to the tests.

My use case for adding this feature is installing private Bitbucket packages from master branch and there is no testing for different branches/commits refs but will be adding it in the future.

Copy link
Owner

@davideicardi davideicardi left a comment

Choose a reason for hiding this comment

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

Thank you!

LGTM! Maybe the only improvement can be to create a fake package inside bitbucket just for test with just the minimum files to speed up tests.

package-lock.json Outdated Show resolved Hide resolved
@quarenw
Copy link
Contributor Author

quarenw commented Jun 1, 2022

Thank you for the review! Makes sense, updated to use a simple package on Bitbucket. Tests now run a reasonable amount of time.

@davideicardi
Copy link
Owner

I see that a test abount concurrency installation has failed. Do you think this can be related to your changes? I don't think so but I need to investigate ...

@quarenw
Copy link
Contributor Author

quarenw commented Jun 6, 2022

I don't think it is related. I have only gotten it to fail once when I run it but am not able to reproduce it when running it myself. Looking at the Actions logs it looks like it has failed previously, before tthe Bitbucket additions, for the same reasons:
https://github.com/davideicardi/live-plugin-manager/runs/5721846444?check_suite_focus=true

image

image

Though in that case node 14 and 12 tests were run while in this last run they were instead cancelled because 16 failed.

Looking at the tests I am not sure why there is the file '/home/runner/work/live-plugin-manager/live-plugin-manager/plugin_packages/install.lock' causing the test to error as I cannot reproduce. Will see if I can replicate.

@davideicardi
Copy link
Owner

Still failing ... strange issue. I will try to investigate.

@quarenw
Copy link
Contributor Author

quarenw commented Jun 16, 2022

Had some time to test and put in a PR for a change to the locking test: #72

@davideicardi
Copy link
Owner

I will merge this PR given that the error seems to be unrelated to the change.
We can try to fix it in #72
Thank you!

@davideicardi davideicardi merged commit 79d057f into davideicardi:master Jun 19, 2022
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.

2 participants