python / docker-bpo Goto Github PK

Currently both docker images are based on fedora:24 and ubuntu:14.04 respectively. It would be nice to build those against latest available ones.

@ezio-melotti I didn't notice this until now that I'm building the openshift version of bpo, when I run rd-start on a clean fresh repo clone I'm getting this. I didn't catch it earlier beacuse I had sets_.pyc in place, when I removed it I'm getting the exact same error. Looks like we need an update, any ideas?

tracker@ac87f66780bb:/$ rd-start
Traceback (most recent call last):
  File "/home/tracker/bin/roundup-server", line 11, in <module>
    run()
  File "/opt/tracker/roundup/roundup/scripts/roundup_server.py", line 978, in run
    httpd = config.get_server()
  File "/opt/tracker/roundup/roundup/scripts/roundup_server.py", line 633, in get_server
    for (name, home) in tracker_homes])
  File "/opt/tracker/roundup/roundup/instance.py", line 327, in open
    return Tracker(tracker_home, optimize=optimize)
  File "/opt/tracker/roundup/roundup/instance.py", line 102, in __init__
    self.detectors = self.get_extensions('detectors')
  File "/opt/tracker/roundup/roundup/instance.py", line 207, in get_extensions
    self._execfile(os.path.join(dirname, name), env)
  File "/opt/tracker/roundup/roundup/instance.py", line 239, in _execfile
    self._exec(self._compile(fname), env)
  File "/opt/tracker/roundup/roundup/instance.py", line 233, in _exec
    exec(obj, env)
  File "/opt/tracker/python-dev/detectors/autonosy.py", line 8, in <module>
    from roundup.anypy.sets_ import set
ImportError: No module named sets_

Roundup moved the setting for the database backend from the db/backend_name file to a setting in the config.ini.
I'm in the process of updating Roundup and the python-dev instance, and once I deploy the update this issue should be taken care of. I already added the backend to config.ini.template, so it should be enough to remove the echo postgres > db/backend_name from some of the scripts and the readme.

These are the notes from doc/upgrading.txt:

Database back end specified in config.ini (REQUIRED)

The db/backend_name file is no longer used to configure the database
backend being used for a tracker. The backend is now configured in the
config.ini file using the backend option located in the [rdbms]
section. For example if db/backend_name file contains sqlite, a new
entry in the tracker's config.ini will need to be created::

  [rdbms]
  ...

  # Database backend.
  # Default:
  backend = sqlite

Once the config.ini file has been updated with the new backend option,
you can safely delete the db/backend_name file.

Note: the backend_name file may be located in a directory other than
db/ if you have configured the database option in the [main]
section of the config.ini file to be something other than db.

I tried to rebuild the image with Ubuntu 16.10, and when I run docker start I got the error:
/init.sh: 7: /init.sh: Syntax error: "(" unexpected (expecting "fi")

I removed the functions from init.sh (i.e. stop_all() {...}) and I was able to rebuild and start the container, however I noticed that those were added in ed0498a for Fedora.

If this doesn't work on Fedora without the function, is there a way to make it work or should we just remove fedora support (why do we even have it?)? FWIW I also tried the syntax function stop_all {...} (without ()) but it doesn't work. Replacing the shebang with /bin/bash might fix the problem for both, but I haven't tried.

Currently after starting the container and running rd-admin init, the db is empty.
There should be a script to easily populate the db, able to quickly:

1. create a few users with different permissions (a Coordinator, a Developer, and a regular user)
2. create a few issues with a few messages each
3. create a specific number of users/issues/messages/etc with specific parameters
4. perhaps import an issue from bpo

This script might also be exploited by the tests.

In order to test GH integration, there should be a script able to send requests like the ones sent by GH when a PR is created or modified or when a PR/commit message mentions bpo-NNNNN.

The script should be able to:

1. read and send payloads from a file
2. generate payloads of the given type, with the values provided or with default values.

This script might also be exploited by the tests.