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

.drone.yml:127-129: Resurrect test-docker-compose pipe... #624

Closed
0pdd opened this issue Nov 1, 2018 · 1 comment
Closed

.drone.yml:127-129: Resurrect test-docker-compose pipe... #624

0pdd opened this issue Nov 1, 2018 · 1 comment
Assignees
Labels
1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable devops work with service options with code or with configs report Put it to completed tasks temporary list for business

Comments

@0pdd
Copy link
Collaborator

0pdd commented Nov 1, 2018

The puzzle 603-db394ed9 from #603 has to be resolved:

shopelectro/.drone.yml

Lines 127 to 129 in afec9c2

# @todo #603:60m Resurrect `test-docker-compose` pipe step.
# See issue details here:
# https://ci.fidals.com/fidals/shopelectro/1006/13

The puzzle was created by duker33 on 01-Nov-18.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd
Copy link
Collaborator Author

0pdd commented Nov 1, 2018

@artemiyds2 @duker33 please pay attention to this new issue.

0pdd referenced this issue Nov 1, 2018
* #fix  Load more button had been failed

* #fix  load_more functions

* #fix  Fix db names at env

* #fix  Fix category page selenium tests processing

* #fix  Skip update_catalog tests

* #fix  Fix linter errors

* #fix  Skip failed `test-docker-compose` pipe step
@0pdd 0pdd mentioned this issue Nov 1, 2018
@duker33 duker33 added 1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time take it any teammate can take this issue and start working with it devops work with service options with code or with configs cleanup everything that do project stronger, flexible, reusable labels Nov 2, 2018
@ArtemijRodionov ArtemijRodionov self-assigned this Dec 5, 2018
@ArtemijRodionov ArtemijRodionov removed the take it any teammate can take this issue and start working with it label Dec 5, 2018
@ArtemijRodionov ArtemijRodionov added the report Put it to completed tasks temporary list for business label Dec 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 hour typical issue size. It's one pdd hour 2 performer can implement issue at his closest convenient time cleanup everything that do project stronger, flexible, reusable devops work with service options with code or with configs report Put it to completed tasks temporary list for business
Projects
None yet
Development

No branches or pull requests

3 participants