-
Notifications
You must be signed in to change notification settings - Fork 26
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
Is the project being maintained? #100
Comments
We are actively using batchiepatchie at AdRoll. I'm not sure about the deployment process in this repo though because we have our own separate private repo called batchiepatchie-deploy that we use for AdRoll batchiepatchie deployments. |
@JonathanAquino-NextRoll thanks for the clarification. That probably means the OSS project is not maintained anymore. Do you know who is the internal owner of the repo by any chance? It would be great if we got the OSS project up to date. I dont mind becoming the maintainer if you folks dont have the interest to maintain the project. |
we still use the code and will make fixes if needed. I guess the deployment part isn't maintained because we have our own deployment code. would you be able to submit a PR if you get the deployment part working? |
@JonathanAquino-NextRoll sure, here is the PR with all the updates required to get this project running :) #99 The code also needed some updates to support my current aws setup, mainly, we dont use a hardcoded loggroup for all teams/tasks, and we dont enable public ips for the jobs. |
@JonathanAquino-NextRoll is there any updates on when will the pr be merged? |
sorry about this - i need to find time to test this. |
@JonathanAquino-NextRoll is there anything i can do to help? |
unfortunately no - I need to find time to relearn how to deploy this internally to make sure nothing breaks and then do it |
I have been using batchiepatchie for years. However I am trying to run it on a new company and the deployment seems to be broken.
I have also noticed plenty of PRs by dependabot are being left ignored.
Is the project being maintained, if not, I would not mind forking it and taking care of it. In my opinion it is still the best OSS way to manage aws batch at scale.
The text was updated successfully, but these errors were encountered: