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

WIP: tar plugin move #1410

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

Use the one from bst-plugins-experimental instead
@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Nov 30, 2019, 15:39

changed the description

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Nov 30, 2019, 15:39

Not sure I will have time to finish this, so please feel free to finish this off

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Nov 30, 2019, 15:40

changed the description

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @valentindavid] on Dec 5, 2019, 10:05

Commented on tests/conftest.py line 115

I do not think we can do that. There are multiple integration tests that runs over multiple plugins. They have to continue to run for tar. And we cannot move them to the bst-experimental-plugins unless we move all of them.

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @BenjaminSchubert] on Dec 5, 2019, 10:10

Commented on tests/conftest.py line 115

Once https://gitlab.com/BuildStream/buildstream/merge_requests/1607 is resolved, that would be done automatically, we would not need to move the tests at all.

Also, those tests would also be run in the bst-plugins-experimental repo.

However, I would feel more comfortable having the testing entirely in place before moving more of those plugins

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Dec 5, 2019, 10:55

Commented on tests/conftest.py line 115

[Gitlab user @valentindavid] mm, can we depend on bst-plugins-external then? I think we already do

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @valentindavid] on Dec 5, 2019, 11:41

Commented on tests/conftest.py line 115

[Gitlab user @jjardon], Yes, we already do. I just pointed out we cannot remove this line, because it disables lots of tests that are not moved to the plugin repository.

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 15, 2020, 11:36

mentioned in merge request bst-plugins-experimental!56

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @BenjaminSchubert] on Jan 15, 2020, 12:23

Commented on tests/conftest.py line 115

Note that this is outdated. We do NOT depend on bst-plugins-experimental anymore.

This should be moved to the other repository at the same time we move the plugin

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 15, 2020, 13:05

added 189 commits

  • c346d9d6...e3fde756 - 186 commits from branch master
  • 7f62c496 - Remove "deb" surce plugin, it has beem moved to bst-plugins-experimental
  • 51885e22 - Remove "tar" plugin
  • 5868a007 - WIP

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 15, 2020, 13:11

added 1 commit

  • 3d9e66b0 - Remove "tar" plugin

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 17, 2020, 04:56

added 2 commits

  • d1171bc - Remove "deb" dource plugin
  • ee2a7919 - Remove "tar" plugin

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 17, 2020, 05:02

added 1 commit

  • fbd19b66 - Remove "tar" plugin

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 17, 2020, 05:09

added 22 commits

  • fbd19b66...a5b23965 - 20 commits from branch master
  • 45507cc - Remove "deb" surce plugin, it has beem moved to bst-plugins-experimental
  • 6ad47e37 - Remove "tar" plugin

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 20, 2020, 10:06

added 10 commits

  • 6ad47e37...35dd0e0e - 9 commits from branch master
  • ba9af19c - Remove "tar" plugin

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 20, 2020, 10:10

resolved all threads

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 20, 2020, 10:12

added 1 commit

  • 855152de - Remove "tar" plugin

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @BenjaminSchubert] on Jan 20, 2020, 10:23

Commented on doc/examples/autotools/project.conf line 15

Those tests will fail without the plugins installed

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @BenjaminSchubert] on Jan 20, 2020, 10:23

Commented on .gitlab-ci.yml line 354

Would it make sense to use the tagged version now that we have tags on bst-plugins-experimental?

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @BenjaminSchubert] on Jan 20, 2020, 10:23

Commented on tox.ini line 176

I think it might be better to use the same version used as for the plugins tests: git+https://gitlab.com/buildstream/bst-plugins-experimental.git[[Gitlab user @]](https://gitlab.com/){env:BST_PLUGINS_EXPERIMENTAL_VERSION:{[config]BST_PLUGINS_EXPERIMENTAL_VERSION}}#egg=bst_plugins_experimental[ostree,deb,tar]

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 20, 2020, 13:32

Commented on .gitlab-ci.yml line 354

mmm, that was the output of git describe --long --abbrev=40 are those new tags annotated tags?

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 20, 2020, 13:36

Commented on tox.ini line 176

changed this line in version 10 of the diff

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 20, 2020, 13:36

added 1 commit

  • 3771f1ab - Remove "tar" plugin

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 20, 2020, 13:37

Commented on tox.ini line 176

Done, thanks

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 20, 2020, 13:41

Commented on doc/examples/autotools/project.conf line 15

[Gitlab user @BenjaminSchubert] is it possible to add a section there or we need to add the plugins to the docker image? or how you propose to solve this?

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @BenjaminSchubert] on Jan 20, 2020, 13:43

Commented on doc/examples/autotools/project.conf line 15

I was wondering if we should go for an approach where we tag tests requiring external plugins ([Gitlab user @pytest].mark.plugins) and then run them at the same time as the source test plugins? That would allow us to have more complete and easy tests setup, while keeping the strict separation for the basic tests and such.

I'm happy to start a ML thread around it if you think that is worth it

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @tpollard] on Jan 21, 2020, 11:42

Commented on doc/examples/autotools/project.conf line 15

Sounds reasonable to me [Gitlab user @BenjaminSchubert] and will be needed for other plugins when they're extracted

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 27, 2020, 12:29

Commented on .gitlab-ci.yml line 354

changed this line in version 11 of the diff

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 27, 2020, 12:29

added 7 commits

  • 3771f1ab...1c3baa29 - 6 commits from branch master
  • 1073ae6 - Remove "tar" plugin

Compare with previous version

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @jjardon] on Jan 27, 2020, 12:30

Commented on .gitlab-ci.yml line 354

Done now, thanks

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @tpollard] on Mar 18, 2020, 13:56

Commented on doc/examples/autotools/project.conf line 15

Are we still aiming for this approach [Gitlab user @BenjaminSchubert]?

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @BenjaminSchubert] on Mar 23, 2020, 17:01

Commented on doc/examples/autotools/project.conf line 15

I would say ideally yes, but I don't have time to take care of this right now. I'm happy to help if someone wants to take over. Otherwise I'll see when I can find time for it.

Unless someone has a better idea. For me it still seems kind of gross, but should work in theory

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @willsalmon] on Mar 25, 2020, 13:46

edit: [Gitlab user @BenjaminSchubert] is https://gitlab.com/BuildStream/buildstream/-/commit/62457c56beac27529b1e52d421b15baf3a070d60 ruffly what you were thinking? then would we add a fixed version of the plug-ins to our CI so they did run in CI? or just leave them as [Gitlab user @jjardon] did only running on the timed tests?

Ahh i had miss read your comment, i need a bit more first

@Cynical-Optimist
Copy link
Author

In GitLab by [Gitlab user @willsalmon] on Mar 25, 2020, 13:47

Those are all you need for the non --integration tests to run but there are ~125 more integration ones that need flagging

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