dsfai2020 / task-and-nutrition-manager Goto Github PK

Flask backend on Heroku (doesn't store data) instead it connects as a client to MongoDb via API.

This was resolved. The grid just needed to be adjusted so that different blocks extend within the primary container.

Make sure the configuration for jenkins (post log in) is completed
Make sure that the github directions are included
Make sure the venv directions are included
Add steps from the already functioning jenkins site on the laptop
Explain

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to Add Another Button
2. Click on the button.
3. Scroll down
4. See error

Expected behavior
Clicking on the Add Another button should create a duplicate of the UI component (Title, Story, Estimate etc...) directly below it.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser FireFox
• Version 121.0.1 64 Bit

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Place files into directories that are relative.
Refactor any code that needs to be rerouted due to the name changes on file.
Run automated tests to ensure that everything works properly.

Put skills in here and make it so that users can drag and drop their skills into equipment slots. Think WoW or Destiny 2 slots.

Cause it to trigger at a step.

This process is to take place on Windows 10 using Docker. While also having Jenkins installed on a container that not only runs, but supports pytest from within docker as well.

ON WINDOWS 10

• Smoke test a python app that runs through powershell
• Get a python docker container file up and running on windows

ON JENKINS/DOCKER

• make sure that it activates a venv and installs the packages from the python env of the repo from the terminal

• make sure that properly runs a basic test

• make sure that it then passes the test

• ensure that the script for jenkins pulls the project in from github to its jenkins directory (which is hosted within Docker)

• Once that is done, connect multiple containers (python and Jenkins) so that python is supported within Docker.

Failure in any of these areas results in a non completion.

Jenkins Terminal

Issue was is resolved. Instead of creating multiple markdown files for the different branch directories I just needed to go into the repository settings on GitHub. From there, go to issues and there is a place to configure the issue template. I'd been able to do this simply by creating the proper directories and file but creating one that didn't originate on the main branch might've caused the issue. It's still unknown EXACTLY what caused it but the issue itself has resolved and my template works. So I'll close this for now unless the need for an update should arise in the future.

X squared.

In coding the squared region is customizable. Make it so that it displays a red circle with a 1 to signify 1 new notification is ready. (UIX)

Docker image needs to be pushed from windows to GitHub
Must install docker
Must successfully build from the docker file
Must run on Linux
The daemon must be activated as well
Must pass test from laptop

In one of the repositories.

Take a screen shot of the timeline and use this as a guide template.

Need account information for Jenkins

To make matters worse, the Home edition of Windows does not allow you to access the Docker Groups and Permissions in the Computer Management tab.

Which means that Docker isn't being recognized by the system when you try to use it with IDE's like VS CODE because terminal uses the one native to Windows.

Add build steps and configure the python backend first.

Linux
Raspberry pi
Windows

All linked and working with Jenkins

Run a pip freeze. Make sure that both the environment and requirements are updated from linux.

Clicking the sign in doesn't connect users to their data.

It should connect them to their account/profile information for the site.

25-50-25 time ratio

• - Feature test (direct)
• Integration test (proximity)
• Regression test (builds)

Keep in mind that:

Windows is running Jenkins from within Docker as a Container.

Linux is running Jenkins locally and not from within Docker.

Both are using the jenkins_test branch to pull repository information from.

Lead: Possible solution at

https://stackoverflow.com/questions/34713765/github-changes-repository-to-the-wrong-language/43520676#43520676

Since the Windows version, on your PC, is running within a container:

Check and see if Jenkins can execute commands in Linux (See if it takes build scripts)

• Copy the build steps from Linux into Windows
• Check if the container running Jenkins will accept linux commands (Does it run on a linux Kernel by default?)
• IF it doesn't, translate a build from the Linux Jenkins (that is currently working) into Windows (terminal friendly).
• Run a smoke test

Successfully activate the environment for the backend on Windows ensuring that all the requirements are there.